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

Why use h_hat interpolated by “nn” as input to the network #5

Open
modestlyh opened this issue Dec 16, 2024 · 4 comments
Open

Why use h_hat interpolated by “nn” as input to the network #5

modestlyh opened this issue Dec 16, 2024 · 4 comments

Comments

@modestlyh
Copy link

I noticed that instead of using only LS estimates, intitial LS channel estimation still uses nn interpolation, which by definition should use only LS estimates, because if interpolation is done, that is equivalent to the network not including the channel estimation piece, I don't know if I'm understanding correctly,but the dimension seems to be an issue again if only LS estimates are used

@SebastianCa
Copy link
Collaborator

Hi @modestlyh,
That's right, there is an initial LS estimation stage. This is useful in multi-user settings and avoids the need to feed (potentially dynamic) pilots during inference (as the value of pilots in 5G NR is dependent on the slot id).

Note that nn stands for nearest neighbor interpolation, meaning the LS estimates at the pilot positions are simply copied to fill the entire resource grid. Compared to the overall complexity of the neural receiver this adds negligible complexity.

@modestlyh
Copy link
Author

@SebastianCa Thanks a lot!

@modestlyh
Copy link
Author

@SebastianCa I would like to ask, has it been tried to train at a high signal to noise range, say 10-25db, and then evaluate at a lower signal to noise range with good results?

@SebastianCa
Copy link
Collaborator

The performance is typically better if the training is done over the entire SNR range, i.e., including low SNR values as well.

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