Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent Path Loss with Minor Terrain Differences #21

Open
jhazentia opened this issue Nov 21, 2024 · 1 comment · May be fixed by #22
Open

Inconsistent Path Loss with Minor Terrain Differences #21

jhazentia opened this issue Nov 21, 2024 · 1 comment · May be fixed by #22
Labels
bug Something isn't working

Comments

@jhazentia
Copy link
Member

jhazentia commented Nov 21, 2024

For a small number of cases, there is a mismatch of path loss between Windows and Linux.
This appears to be a numeric rounding issue related to the LinearLeastSquaresFit function.

After further digging, this appears to be due to small differences in terrain profile. The
same Python code and terrain data was used to create the terrain files on Windows and Linux,
but different OS results in small differences in terrain profile. The extremely small
differences (max difference approx. 1E-9) can cause > 1 dB difference in pathloss in some
cases due to numeric error in the LinearLeastSquaresFit function.

I attached a couple of examples, I have more available if needed.

Input Files:
case_1_itm_inputs.txt
case_2_itm_inputs.txt

Terrain Files:
case_2_windows_pfl.txt
case_1_linux_pfl.txt
case_1_windows_pfl.txt
case_2_linux_pfl.txt

Output Files:
case_1_itm_command_output_windows_pfl.txt
case_2_itm_command_output_linux_pfl.txt
case_2_itm_command_output_windows_pfl.txt
case_1_itm_command_output_linux_pfl.txt

@jhazentia
Copy link
Member Author

I plan to submit a PR with additional details that adds rounding to LinearLeastSquaresFit function to fix this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants