Welcome to pyrpl Discussions!

[peteasa]

👋 Welcome!

I am using Discussions as a place to connect with other members of our community to discuss my personal proposals for python3 code changes to pyrpl. I hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

[peteasa]

To kick things off.. if you want to use my consolidated_python3 branch this is how my simple install works:

Step by step instructions for "simple install" using Ubuntu 24.04 LTS:
First setup RedPitaya using the "normal" installation process for v0.94 - 2.00-37 - Branch 2024.3 see - https://redpitaya.readthedocs.io/en/latest/quickStart/SDcard/SDcard.html

@rp-xxxxxx:~$ cat /opt/redpitaya/version.txt
Red Pitaya GNU/Linux Ecosystem
Version: 2.00-a0457d3aa
Build: 37
Branch: 
Commit: a0457d3aa595ca790b8c4386990f963f775e6c03
U-Boot: "redpitaya-v2022.1"
Linux Kernel: "branch-redpitaya-v2024.1"
Pro Applications: ""

Next on ubuntu host install the necessary python3 packages used by pyrpl:

sudo apt install python3-ipython python3-numpy python3-pandas python3-scp python3-paramiko python3-scipy python3-ruamel.yaml python3-qtpy python3-qasync python3-pyqtgraph python3-nest-asyncio python3-matplotlib python3-yaml

Next create your project directory and link to the pyrpl library

git clone https://github.com/github.com/peteasa/pyrpl
cd pyrpl
git checkout consolidate_python3
cd ..
mkdir myproject
cd myproject
ln -s ../pyrpl/pyrpl .

Now you are set to create python3 code or create .ipynb files in your project folder and connect using import pyrpl.

There are other install processes that may work better for you. In my case this is simple and easy so I have no need for other python package managers or virtual environments.

The https://github.com/peteasa/pyrpl/tree/consolidate_python3 branch is my work in progress branch.. but it works so use if it you want. Best also check out https://github.com/pyrpl-fpga/pyrpl main branch and https://github.com/redpitaya/pyrpl main branch.

If you want a "ready made" test project then why not clone my https://github.com/peteasa/pyrpl_testbench code. I have put there a number of the things that I have tried whilst characterising the pyrpl code.

[JohannesWes]

Thank you for the extensive explanation. I have gotten pyrpl running at least from a jupyter notebook the way you described it and was able to read values from the oscilloscope module in python. I still get the same bug if I try to start the gui from the notebook, as in issue pyrpl-fpga#520 of the main repo. I'll see if I can solve this maybe once I've understood pyrpl and maybe contribute something. I have to admit also, that I'm on windows (just as the creator of issue pyrpl-fpga#520) and dont know if this gui bug happens on ubuntu too.

[peteasa]

Thanks for your efforts! I do not expect the gui launch to work from within a notebook with my version, although I get a different symptom to pyrpl-fpga#520.

In my case the file https://github.com/peteasa/pyrpl/blob/consolidate_python3/pyrpl/async_utils.py is a bit of a mess as described in RedPitaya#7 (comment) and more detail for my case in RedPitaya#7 (comment). Basically pyrpl uses Qt in the background for async operation as well as for the GUI, however there is a clash between ipython / jupyter and pyrpl. I am sure that some bright person will be able to fix this for all the various use cases of pyrpl, however I only expect the gui to work from the command line:

python3 -m pyrpl example_filename

If you want to try out the main branch version of async_utils.py just take a local copy and overwrite my version of async_utils.py and you might get a different experience! Let me know.. its possible that for other environments my version of async_utils.py is just no good!

[peteasa]

by the way one obvious thing to try if you have startup problems is to remove the previous run configuration or simply not use a configuration file.. so the pyrpl_user_dir/config folder contains the yml file that is created when your launch pyrpl with a configuration file

p = pyrpl.Pyrpl(config = 'myconfig', ....

This has good and bad features.. the good feature is that when using the gui you can "save" the current state in myconfig.yml and restore this at startup of the next session. one of the bad features is that configuration from your first run can give you unexpected results with the next run..

I have found this a couple of times and have fixed it by either not using a configuration file or by deleting the old .yml files before a new session. So for example if for some reason to exit early from the application and the .yml file is not correctly saved then it can crash launching a new session. You end up thinking its something that you changed in the code when infact all you need to do is delete the .yml file and it springs back into life when your start your application!

[JohannesWes]

I am sorry, I mixed something up. I dont get the pyrpl-fpga#520 error, I get an error in the valid_frequencies array, connected to the NetworkAnalyzer module I think.

I'll try, reading through the pyrpl code currently. Thank you!