pcdshub / pcdshub/engineering_tools
epicsArchChecker does not call epicsArchVerify correctly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 5
- Forks
- 36
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 3
Description
The environment previously used for epicsArchVerify, no longer exists. It should be changed to source the relevant hutch's daq environment, e.g.
source ~ABCopr/scripts/setup_env.sh
ued will need special handling
/cds/home/opr/uedopr/git/lcls2_241110/install/bin/epicsArchVerify
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
Locate the epicsArchChecker entry point and inspect how it invokes epicsArchVerify. Compare that setup with source ~ABCopr/scripts/setup_env.sh, then account for the special /cds/home/opr/uedopr/git/lcls2_241110/install/bin/epicsArchVerify path; done means the checker uses the relevant hutch DAQ environment and handles ued.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100