-
Notifications
You must be signed in to change notification settings - Fork 17
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
Comments
Hi,
|
Example: In this test I use Python's matlab.engine for call MATLAB functions such as Details about MATLAB API: |
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 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. |
that sounds good. PRs are welcome. |
Ok, let me close current issue and I'll come back later with PRs. Thanks! |
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:
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.
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?
The text was updated successfully, but these errors were encountered: