Check to tun post new galil driver install

Open Beginner friendly
#9,023 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Domain
testing

Research direction

Start by locating pre-upgrade files matching C:\Instrument\Var\autosave\GALIL* with the settings keyword, then run asverify for each Galil controller as shown. Compare the output against the listed expected differences and ignore the explicitly permitted changes. Done means no other unexpected PV value differences remain.

Written by the indexing model from the issue text.

Description

autosave check

locate autosave files in c:\instrumemt\var\autosave\GALIL* with the settings keyword in them from a date prior to the upgrade, then pass name to asverify command for each galil controller e.g.

C:\Instrument\Apps\EPICS>asverify C:\Instrument\Var\autosave\GALIL_02\GALIL_02_settings.sav_260731-182226

This will show PVs that differ in value before and after upgrade. All you should see is:

  • HOMEVAL_SP no longer exists, but it should say its saved value was 0
  • _EDEL_SP will have a different value, it is not autosave in the new driver but there is logic to pass its previous value to the new PV _ENC_TOLERANCE_SP
  • If it says live values of USWITCH_CMD is 0 but saved value is 1 that is fine, we want 0 for this
  • If ONDELAY_SP has chanegd from 0.000000 to 0.001000 fine as well
  • if may talk about FTRANSFORM, RTRANSFORM changing from scalar/array – these are for MTRxx09 and above so can be ignored
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ISISComputingGroup/IBEX

All issues in ISISComputingGroup/IBEX

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.