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

Dimension discrepancy for 'a' vs 'tau'/'theta_r' in compute_paths() #547

Closed
lllck opened this issue Aug 16, 2024 · 1 comment
Closed

Dimension discrepancy for 'a' vs 'tau'/'theta_r' in compute_paths() #547

lllck opened this issue Aug 16, 2024 · 1 comment

Comments

@lllck
Copy link

lllck commented Aug 16, 2024

Hello! Could you please clarify why the dimension of 'a' in the paths returned by scene.compute_paths() is [batch_size, num_rx, num_rx_ant, num_tx, num_tx_ant, max_num_paths, num_time_steps], while other parameters like 'tau' and 'theta_r' have dimensions of [batch_size, num_rx, num_tx, max_num_paths]? Why do these other parameters lack the antenna number dimensions?

@lllck lllck changed the title "Discrepancy in Antenna Dimension for 'a' Parameter Compared to 'tau' and 'theta_r' in scene.compute_paths() Output" Dimension discrepancy for 'a' vs 'tau'/'theta_r' in compute_paths() Aug 16, 2024
@SebastianCa
Copy link
Collaborator

Hi @lllck,
this happens if you run the ray tracer with synthetic_array=True which means ray tracing is done from the center of the antenna array. Thus, only one path length exists. If you set synthetic_array=False you will get individual paths for each antenna element and, thus, the additional dimensions for tau.

Closing this issue as the described behaviour is expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants