Closed teddyrendahl closed 6 years ago
Merging #46 into master will decrease coverage by
4.89%
. The diff coverage is88%
.
@@ Coverage Diff @@
## master #46 +/- ##
=========================================
- Coverage 91.68% 86.78% -4.9%
=========================================
Files 6 6
Lines 457 386 -71
=========================================
- Hits 419 335 -84
- Misses 38 51 +13
Impacted Files | Coverage Δ | |
---|---|---|
lightpath/path.py | 82.51% <100%> (-7.16%) |
:arrow_down: |
lightpath/controller.py | 77.5% <60%> (-11.39%) |
:arrow_down: |
lightpath/ui/gui.py | 92.43% <87.5%> (+2.26%) |
:arrow_up: |
lightpath/ui/widgets.py | 89.74% <0%> (-10.26%) |
:arrow_down: |
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact)
,ø = not affected
,? = missing data
Powered by Codecov. Last update 191e5df...1220122. Read the comment docs.
Description
This pull request makes
lightpath
work withhappi > 0.5.x
andpcdsdevices > 0.3.x
. The major changes that affected the lightpath were:device.z
had to be changed todevice.md.z
MPS
devices are no longer associated with devices. They will be in thehappi
database as a separate objectFor the actual
BeamPath
code, I deprecated all the references to the MPS system. In the future, we will just create a small objectMPSSummary
that manages the entire MPS system for a beamline. These will also be displayed in their own panel in the purpose of the GUI.The most frustrating change is that the UI used to treat
happi.Device
objects andpcdsdevices
objects the same. Now that the latter has metadata contained in themd
attribute, that code does not work. For now I have just decided to remove them from the main lightpath GUI. I think the answer in the end is to have a separate panel where disconnected devices are displayed.Motivation and Context
Should now be importable in newer releases of
pcds-envs
In the end, this PR is a step back in terms of feature set but nothing that was heavily used was taken away. It can be used in the new
hutch-python
environment. The rest will be addressed during the UI re-release.How Has This Been Tested?
Updated tests to match new library expectations. Also created a
BeamPath
in the currentmfxpython
environment to do a live check.