8. Trajectory transformations (“on-the-fly” transformations)¶
In MDAnalysis, a transformation is a function that modifies the data
for the current Timestep
and returns the
Timestep
. For instance, coordinate transformations, such as
PBC corrections and molecule fitting are often required for some
analyses and visualization. Transformation functions
(transformation_1
and transformation_2
in the following
example) can be called by the user for any given Timestep
of
the trajectory,
u = MDAnalysis.Universe(topology, trajectory)
for ts in u.trajectory:
ts = transformation_2(transformation_1(ts))
where they change the coordinates of the timestep ts
in
place. There is nothing special about these transformations except
that they have to be written in such a way that they change the
Timestep
in place.
As described under Workflows, multiple transformations can be
grouped together and associated with a trajectory so that the
trajectory is transformed on-the-fly, i.e., the data read from the
trajectory file will be changed before it is made available in, say,
the AtomGroup.positions
attribute.
The submodule MDAnalysis.transformations
contains a
collection of transformations (see Transformations in MDAnalysis) that
can be immediately used but one can always write custom
transformations (see Creating transformations).
8.1. Workflows¶
Instead of manually applying transformations, it is much more convenient to associate a whole workflow of transformations with a trajectory and have the transformations be called automatically.
A workflow is a sequence (tuple or list) of transformation functions that will be applied in this order. For example,
workflow = [transformation_1, transformation_2]
would effectively result in
ts = transformation_2(transformation_1(ts))
for every time step in the trajectory.
One can add a workflow using the
Universe.trajectory.add_transformations
method
of a trajectory (where the list workflow
is taken from the example
above),
u.trajectory.add_transformations(*workflow)
or upon Universe
creation using the keyword argument transformations:
u = MDAnalysis.Universe(topology, trajectory, transformations=workflow)
Note that in these two cases, the workflow cannot be changed after having being added.
8.2. Creating transformations¶
A transformation is a function that takes a
Timestep
as input, modifies it, and
returns it.
A simple transformation that takes no other arguments but a Timestep
can be defined as the following example:
def up_by_2(ts):
"""
Translate all coordinates by 2 angstroms up along the Z dimension.
"""
ts.positions = ts.positions + np.array([0, 0, 2], dtype=np.float32)
return ts
If the transformation requires other arguments besides the Timestep
,
the transformation takes these arguments, while a wrapped function takes the
Timestep
object as argument. So, a transformation can be roughly
defined as follows:
def up_by_x(distance):
"""
Creates a transformation that will translate all coordinates by a given amount along the Z dimension.
"""
def wrapped(ts):
ts.positions = ts.positions + np.array([0, 0, distance], dtype=np.float32)
return ts
return wrapped
An alternative to using a wrapped function is using partials from functools
. The
above function can be written as:
import functools
def up_by_x(ts, distance):
ts.positions = ts.positions + np.array([0, 0, distance], dtype=np.float32)
return ts
up_by_2 = functools.partial(up_by_x, distance=2)
See MDAnalysis.transformations.translate()
for a simple
example of such a type of function.
8.3. Transformations in MDAnalysis¶
The module MDAnalysis.transformations
contains transformations that can
be immediately used in your own workflows. In order to use
any of these transformations, the module must first be imported:
import MDAnalysis.transformations
A workflow can then be added to a trajectory as described above.
See Currently implemented transformations for more on the existing
transformations in MDAnalysis.transformations
.
8.4. How to transformations¶
Translating the coordinates of a single frame (although one would normally add the transformation to a workflow, as shown in the subsequent examples):
u = MDAnalysis.Universe(topology, trajectory)
new_ts = MDAnalysis.transformations.translate([1,1,1])(u.trajectory.ts)
Create a workflow and add it to the trajectory:
u = MDAnalysis.Universe(topology, trajectory)
workflow = [MDAnalysis.transformations.translate([1,1,1]),
MDAnalysis.transformations.translate([1,2,3])]
u.trajectory.add_transformations(*workflow)
Giving a workflow as a keyword argument when defining the universe:
workflow = [MDAnalysis.transformations.translate([1,1,1]),
MDAnalysis.transformations.translate([1,2,3])]
u = MDAnalysis.Universe(topology, trajectory, transformations=workflow)
8.5. Currently implemented transformations¶
- 8.5.1. Trajectory translation —
MDAnalysis.transformations.translate
- 8.5.2. Trajectory rotation —
MDAnalysis.transformations.rotate
- 8.5.3. Trajectory Coordinate Averaging —
MDAnalysis.transformations.positionaveraging
- 8.5.4. Fitting transformations —
MDAnalysis.transformations.fit
- 8.5.5. Wrap/unwrap transformations —
MDAnalysis.transformations.wrap