Skip to content

Conversation

@T-Nicholls
Copy link
Collaborator

@T-Nicholls T-Nicholls commented Aug 2, 2018

Final lot of changes to the .rst docs files.

@T-Nicholls T-Nicholls changed the title Documentation amendments. Documentation amendments Aug 2, 2018
@coveralls
Copy link

Coverage Status

Coverage remained the same at 94.541% when pulling 6c979a8 on T-Nicholls:docChanges into 16700f5 on willrogers:master.

@coveralls
Copy link

coveralls commented Aug 2, 2018

Coverage Status

Coverage remained the same at 94.541% when pulling d6d1ddc on T-Nicholls:docChanges into 16700f5 on willrogers:master.

docs/index.rst Outdated
Elements may be grouped into families (an element may be in more than one family), and requested from the lattice object in those families. The current control system integrates with EPICS and uses EPICS PV (process variable) objects to tell EPICS which IOC (input/output controller) to communicate with. The type of the PV specifies which operations can be performed, there are two types of PV: readback, which can only be used to retrieve data; and setpoint, which can be used to set a value as well as for retrieving data. A single component may have both types; and so some methods take 'handle' as an argument, this is to tell the control system which PV to use when interfacing with EPICS, readback ('pytac.RB') or setpoint ('pytac.SP').

Data may be requested in ``ENG`` or ``PHYS`` units and will be converted as appropriate. Two types of unit conversion are available: Polynomial (often used for linear conversion) and Piecewise Cubic Hermite Interpolating Polynomial (Pchip; often used for magnet data where field may not be linear with current). In the case that measurement data (used to set up the conversion objects) is not in the same units as the physical models, further functions may be given to these objects to complete the conversion correctly.
Data may be requested or sent in engineering (``ENG``) or physics (``PHYS``) units and will be converted as appropriate. This conversion is a fundamental part of how pytac integrates with the physical accelerator, as physics units are what our description of the accelerator works with (e.g. the current in a magnet) and engineering units are what the IOCs on the physical components use (e.g. the current in a magnet). Two types of unit conversion are available: Polynomial (``PolyUnitConv``; often used for linear conversion) and Piecewise Cubic Hermite Interpolating Polynomial (``PchipUnitConv``; often used for magnet data where field may not be linear with current). In the case that measurement data (used to set up the conversion objects) is not in the same units as the physical models, further functions may be given to these objects to complete the conversion correctly.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You've put 'e.g. the current in a magnet' for both physics and engineering here. The first one should be 'e.g. the magnetic field inside a magnet'



- Import pytac and initialise the ``VMX`` ring mode::
- Import pytac and initialise from the ``VMX`` ring model::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should say:

Import pytac and initialise the 'VMX' lattice:

@T-Nicholls
Copy link
Collaborator Author

Corrected the wording for both topics, should be good to merge now.

@willrogers willrogers merged commit b2ea6dc into DiamondLightSource:master Aug 2, 2018
@T-Nicholls T-Nicholls deleted the docChanges branch August 7, 2018 17:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants