pycroscopy / pycroscopy/asyncroscopy
LLM in notebooks should not have a pyTango dependency.
Open
Beginner friendly
Nobody has claimed this yet.
bug
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 11
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 2
Description
In the moment, llm notebooks have a pyTango dependency.
Actually it looks like that the llm is started as a pyTango device.
The client should however only comunicate with the MCP server, and should not have any other dependencies.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the LLM notebooks and their dependency declarations first, then trace how the client connects to the MCP server and where pyTango is introduced. Done means the notebooks communicate through the MCP server without requiring pyTango; run the relevant notebook or project checks to verify this.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- ai, backend
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100