simonsobs / simonsobs/sodetlib
pysmurf issue of epics failed to respond
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 0
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 4
Description
Hello,
We are currently having this issue of running S = cfg.get_smurf_control() in jupyter notebook
Command failed: smurf_server_s2:AMCc:SmurfApplication:EnabledBays, that's related to epics failed to respond
and in ipython it shows
In [1]: CA.Client.Exception...............................................
Warning: "Virtual circuit disconnect"
Context: "localhost:5064"
Source File: ../cac.cpp line 1223
Current Time: Mon Jul 10 2023 18:06:59.475148447
i think this might be related to issues #353 that happened a month ago, which was fixed by hammering for several times(!!). and it's kind of random. After rerunning S=cfg.get_smurf_control(), it 's back to normal
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
Start by reproducing the failure from a Jupyter notebook at cfg.get_smurf_control(), then compare the behavior with issue #353 and the IPython virtual-circuit warning. Trace the entry point and its connection handling; done means identifying a reliable cause and preventing or clearly reporting the intermittent EPICS response failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100