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

Contribution #1

Closed
vborchsh opened this issue Apr 21, 2023 · 6 comments
Closed

Contribution #1

vborchsh opened this issue Apr 21, 2023 · 6 comments

Comments

@vborchsh
Copy link
Contributor

Dear Benjamin,

Very interesting work! Actually, I do the same things and I will be happy to contribute in the project instead of standalone mess. You will find my stuff here: https://github.com/vborchsh/pynrl1/tree/develop/pynrl1

So, I have couple of questions:

  1. What would you mind about refactoring repo structure for clear division between tests and functional modules? It won't affect to ipynb examples or any other.

  2. Github CI obviously has no MATALB instance. I cover Python modules with MATLAB references thanks to Python API. May I keep it "as is" for offline checks?

@catkira
Copy link
Owner

catkira commented Apr 21, 2023

Hi,

  1. yes I think that would be good
  2. I don't understand that, can You give an example of a "MATLAB reference"?

@vborchsh
Copy link
Contributor Author

I don't understand that, can You give an example of a "MATLAB reference"?

Example:
https://github.com/vborchsh/pynrl1/blob/develop/tests/test_nrPBCH.py

In this test I use Python's matlab.engine for call MATLAB functions such as eng.nrPBCH(...) literally from MATLAB. Then, I use MATLAB arrays to check my Python's implementation.

Details about MATLAB API:
https://www.mathworks.com/help/matlab/matlab-engine-for-python.html

@catkira
Copy link
Owner

catkira commented Apr 21, 2023

Ah I see. Yes I think it does not hurt if they are kept in the code, as long as there are still pure python tests which can run without Matlab.
I had a quick look at Your code, so far the things You implemented look fairly identical to the ones I did. What is Your plan for implementing next?

@vborchsh
Copy link
Contributor Author

vborchsh commented Apr 21, 2023

I concentrated on downlink part. So, I'm going to implement PDSCHDMRS+Indices, PDSCHPTRS+Indices and PDCCH+Indices functions to cover my current work. Then - PDSCH in general, probably, with limited functionality in the beginning.

Plus certain configuration classes, needed for mentioned functions.

@catkira
Copy link
Owner

catkira commented Apr 21, 2023

that sounds good. PRs are welcome.

@vborchsh
Copy link
Contributor Author

Ok, let me close current issue and I'll come back later with PRs. Thanks!

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