Encapsulating custom code into Gym environments: A turning controller#

Summary: In this tutorial, we will demonstrate how one can build controllers at different levels of abstraction by implementing Gym environments encoding variable amounts of preprogrammed computation. As an example, we will refactor the code we wrote in the hybrid controller tutorial and implement turning by asymmetrically modulating the amplitude and frequencies of CPGs.

Gym environments and MDP#

So far, we have interacted with the NeuroMechFly class which implements the Gym interface: it has an action space (input given by the user), an observation space (output returned to the user), a .step(...) method, a .reset(...) method, and a .render(...) method. The action and observation spaces of NeuroMechFly are as follows:

  • Action space:

    • “joints”: 42-dimensional real vector ∈ [0, 2π] indicating joint angles (in default position control mode)

    • “adhesion”: 6-dimensional integer vector ∈ {0, 1} indicating whether adhesion is turned on for each leg

  • Observation space:

    • “joints”: shape (3, 42) real array indicating joint angles (0th row), velocities (1st row), and torques (2nd row)

    • “fly”: shape (4, 3) real array indicating fly xyz positions (0th row), xyz velocities (1st row), yaw-pitch-roll angles (2nd row), and yaw-pitch-roll velocities (3rd row)

    • “contact_forces”: shape (N, 3) - contact forces, in xyz directions, of the N segments defined in contact_sensor_placements

    • “end_effectors”: shape (6, 3) - xyz positions of the six legs in the order of LF, LM LH, RF, RM, RH

    • “fly_orientation”: shape (3,) - unit vector indicating the fly’s heading orientation

The FlyGym package is designed to be expandable: the user can implement their own Gym environments with different action and observation spaces and implement different logics (eg. preprogrammed premotor computation and sensory processing). This is illustrated in the figure below:

https://github.com/NeLy-EPFL/_media/blob/main/flygym/mdp.png?raw=true

In the hybrid controller that we have implemented, the underlying CPG network and the correction mechanisms can be considered the user-defined premotor computation (purple). The whole controller can be considered the box indicating the Markov Decision Process (MDP). Here, we will add a 2D descending signal that encodes turning. The action and observation spaces of our MDP “box” are as follows:

  • Action space: a 2-dimensional real vector describing the velocity on each side of the body. Although in principle the range of the amplitude is unrestricted, its absolute value shouldn’t go far beyond 1 because otherwise the steps become very unrealistic.

  • Observation space: same as above (no sensory processing logic indicated in cyan)

Approach for turning#

We will use a 2-dimensional representation of descending signals \([\delta_L, \delta_R] \in \mathbb{R}^2\) to modulate the amplitude and direction of leg CPGs on each side of the body. Specifically, we will modulate the intrinsic amplitude \(R'\) and intrinsic frequency \(\nu'\) on each side by:

\[R'(\delta) = |\delta|\]
\[\begin{split}\nu_i'(\delta) = \begin{cases} \nu_i & \text{if } \delta>0\\ -\nu_i & \text{otherwise} \end{cases}\end{split}\]

In other words, the magnitude of the descending signal controls the amplitude of stepping (as a gain applied to the originally recorded step size); the sign of the descending signal controls the direction of stepping. Of course, this is a very simplified model of turning. Perhaps the most unrealistic aspect of it is that it assumes that the step size spans linearly from 0 to 1x the recorded “real” step size. This is an area for future improvement.

Implementing the HybridTurningController class#

A key idea of the Gym interface is that it allows users to encapsulate the control logic in a Gym environment (a MDP), and expose only the input and output (action and observation) to the controller. This is achieved using class inheritance in Python. Briefly, it allows a new class (subclass or child class) to inherit attributes and methods from an existing class (base class or parent class), enabling code reuse and the creation of hierarchical relationships between classes. Refer to the tutorial linked above to familiarize yourself with this concept.

All Gym environments inherit from the gymnasium.Env class. You can refer to the API reference of this class for a full specification, or this page for a tutorial on how to make your own custom environment. The NeuroMechFly class we have used so far inherits from it and therefore complies with its specifications. Here, we will build a HybridTurningController class that inherits from NeuroMechFly to provide a simplified interface to control turning via a 2D input space, which can be interpreted as a descending code.

First, let’s do the necessary imports and define the default parameter as before:

 1import numpy as np
 2import matplotlib.pyplot as plt
 3from tqdm import trange
 4from gymnasium import spaces
 5from gymnasium.utils.env_checker import check_env
 6
 7from flygym.mujoco import Parameters, NeuroMechFly
 8from flygym.mujoco.examples.common import PreprogrammedSteps
 9from flygym.mujoco.examples.cpg_controller import CPGNetwork
10
11
12_tripod_phase_biases = np.pi * np.array(
13    [
14        [0, 1, 0, 1, 0, 1],
15        [1, 0, 1, 0, 1, 0],
16        [0, 1, 0, 1, 0, 1],
17        [1, 0, 1, 0, 1, 0],
18        [0, 1, 0, 1, 0, 1],
19        [1, 0, 1, 0, 1, 0],
20    ]
21)
22_tripod_coupling_weights = (_tripod_phase_biases > 0) * 10
23
24_default_correction_vectors = {
25    # "leg pos": (Coxa, Coxa_roll, Coxa_yaw, Femur, Fimur_roll, Tibia, Tarsus1)
26    "F": np.array([0, 0, 0, -0.02, 0, 0.016, 0]),
27    "M": np.array([-0.015, 0, 0, 0.004, 0, 0.01, -0.008]),
28    "H": np.array([0, 0, 0, -0.01, 0, 0.005, 0]),
29}
30_default_correction_rates = {"retraction": (500, 1000 / 3), "stumbling": (2000, 500)}

Now, we will define the __init__ method of our HybridTurningNMF class. The complete, functional class definition can be found on our GitHub repository. You can import it with from flygym.mujoco.examples.turning_controller import HybridTurningNMF.

We start with initializing the parent class by calling super().__init__(...). This basically calls the __init__ logic of the parent NeuroMechFly class using the specified parameters:

class HybridTurningNMF(NeuroMechFly):
    def __init__(
        self,
        preprogrammed_steps=None,
        intrinsic_freqs=np.ones(6) * 12,
        intrinsic_amps=np.ones(6) * 1,
        phase_biases=_tripod_phase_biases,
        coupling_weights=_tripod_coupling_weights,
        convergence_coefs=np.ones(6) * 20,
        init_phases=None,
        init_magnitudes=None,
        stumble_segments=["Tibia", "Tarsus1", "Tarsus2"],
        stumbling_force_threshold=-1,
        correction_vectors=_default_correction_vectors,
        correction_rates=_default_correction_rates,
        amplitude_range=(-0.5, 1.5),
        seed=0,
        **kwargs,
    ):
        # Initialize core NMF simulation
        super().__init__(**kwargs)

        ...

We can save the arguments as class attributes:

...

if preprogrammed_steps is None:
    preprogrammed_steps = PreprogrammedSteps()
self.preprogrammed_steps = preprogrammed_steps
self.intrinsic_freqs = intrinsic_freqs
self.intrinsic_amps = intrinsic_amps
self.phase_biases = phase_biases
self.coupling_weights = coupling_weights
self.convergence_coefs = convergence_coefs
self.stumble_segments = stumble_segments
self.stumbling_force_threshold = stumbling_force_threshold
self.correction_vectors = correction_vectors
self.correction_rates = correction_rates
self.amplitude_range = amplitude_range
self.draw_corrections = draw_corrections

...

Next, we need to override the action space of NeuroMechFly. This is done by defining a new Gym space object. Gym provides an interface for various space types. An non-exhaustive list includes Box for a possibly-bounded box in \(\mathbb{R}^n\), Discrete for a finite set of options, Text for text, and various composite spaces such as Dict, Tuple, Sequence, Graph. Here, we will define the descending space as a Box space. We won’t change the observation space definition since we will return NeuroMechFly’s observation as is:

...

# Define action and observation spaces
self.action_space = spaces.Box(*amplitude_range, shape=(2,))

...

Then, we will initialize the CPG network that we defined in the CPG tutorial:

...

# Initialize CPG network
self.cpg_network = CPGNetwork(
    timestep=self.sim_params.timestep,
    intrinsic_freqs=intrinsic_freqs,
    intrinsic_amps=intrinsic_amps,
    coupling_weights=coupling_weights,
    phase_biases=phase_biases,
    convergence_coefs=convergence_coefs,
    seed=seed,
)
self.cpg_network.reset(init_phases, init_magnitudes)

...

We will then initialize variables tracking the amount of retraction and stumbling correction as we did in the hybrid controller tutorial:

...

# Initialize variables tracking the correction amount
self.retraction_correction = np.zeros(6)
self.stumbling_correction = np.zeros(6)

...

Finally, we will find the contact sensors for stumbling detection as we did before. This time, we define it as a method of our new class:

def _find_stumbling_sensor_indices(self):
    stumbling_sensors = {leg: [] for leg in self.preprogrammed_steps.legs}
    for i, sensor_name in enumerate(self.contact_sensor_placements):
        leg = sensor_name.split("/")[1][:2]  # sensor_name: eg. "Animat/LFTarsus1"
        segment = sensor_name.split("/")[1][2:]
        if segment in self.stumble_segments:
            stumbling_sensors[leg].append(i)
    stumbling_sensors = {k: np.array(v) for k, v in stumbling_sensors.items()}
    if any(
        v.size != len(self.stumble_segments) for v in stumbling_sensors.values()
    ):
        raise RuntimeError(
            "Contact detection must be enabled for all tibia, tarsus1, and tarsus2 "
            "segments for stumbling detection."
        )
    return stumbling_sensors

… and we can all it in __init__. This concludes the definition of our __init__ method:

...

# Find stumbling sensors
self.stumbling_sensors = self._find_stumbling_sensor_indices()

Next, we shall define the reset method of our HybridTurningController class. This involves resetting the underlying NeuroMechFly simulation — as before, we will call super().reset(...) to drop in the reset method of the parent class. Then, we will reset the CPG network and the stumbling amounts. Note that the **kwargs argument is required to fully comply with the Gym API. In general, this gives the user more flexibility to pass additional arguments when initializing the Gym environment.

def reset(self, seed=None, init_phases=None, init_magnitudes=None, **kwargs):
    obs, info = super().reset(seed=seed)
    self.cpg_network.random_state = np.random.RandomState(seed)
    self.cpg_network.reset(init_phases, init_magnitudes)
    self.retraction_correction = np.zeros(6)
    self.stumbling_correction = np.zeros(6)
    return obs, info

Now, we are ready to implement the most important step method. We start by updating the intrinsic amplitudes and frequencies of the CPGs as formulated above:

def step(self, action):
    """Step the simulation forward one timestep.

    Parameters
    ----------
    action : np.ndarray
        Array of shape (2,) containing descending signal encoding
        turning.
    """
    # update CPG parameters
    amps = np.repeat(np.abs(action[:, np.newaxis]), 3, axis=1).flatten()
    freqs = self.intrinsic_freqs.copy()
    freqs[:3] *= 1 if action[0] > 0 else -1
    freqs[3:] *= 1 if action[1] > 0 else -1
    self.cpg_network.intrinsic_amps = amps
    self.cpg_network.intrinsic_freqs = freqs

We will once again use super() to call the get_observation method of the parent NeuroMechFly class:

...

# get current observation
obs = super().get_observation()

...

Next, we check whether the condition is met for the retraction of any leg. To do this, we define a helper method:

def _retraction_rule_find_leg(self, obs):
    """Returns the index of the leg that needs to be retracted, or None
    if none applies."""
    end_effector_z_pos = obs["fly"][0][2] - obs["end_effectors"][:, 2]
    end_effector_z_pos_sorted_idx = np.argsort(end_effector_z_pos)
    end_effector_z_pos_sorted = end_effector_z_pos[end_effector_z_pos_sorted_idx]
    if end_effector_z_pos_sorted[-1] > end_effector_z_pos_sorted[-3] + 0.05:
        leg_to_correct_retraction = end_effector_z_pos_sorted_idx[-1]
    else:
        leg_to_correct_retraction = None
    return leg_to_correct_retraction

… and call it in the step method:

...

# Retraction rule: is any leg stuck in a gap and needing to be retracted?
leg_to_correct_retraction = self._retraction_rule_find_leg(obs)

...

Next, we can step the CPG:

...

self.cpg_network.step()

...

Then, we write a loop to go through each of the legs. In this loop, we update the correction amount for both the retraction rule and the stumbling rule. As before, we assign the retraction rule priority. We then calculate the target joint angles using the preprogrammed step class and decide whether adhesion should be turned off for swinging:

...

joints_angles = []
adhesion_onoff = []
for i, leg in enumerate(self.preprogrammed_steps.legs):
    # update retraction correction amounts
    self.retraction_correction[i] = self._update_correction_amount(
        condition=(i == leg_to_correct_retraction),
        curr_amount=self.retraction_correction[i],
        correction_rates=self.correction_rates["retraction"],
        viz_segment=f"{leg}Tibia" if self.draw_corrections else None,
    )
    # update stumbling correction amounts
    self.stumbling_correction[i] = self._update_correction_amount(
        condition=self._stumbling_rule_check_condition(obs, leg),
        curr_amount=self.stumbling_correction[i],
        correction_rates=self.correction_rates["stumbling"],
        viz_segment=f"{leg}Femur" if self.draw_corrections else None,
    )
    # get net correction amount
    net_correction = self._get_net_correction(
        self.retraction_correction[i], self.stumbling_correction[i]
    )

    # get target angles from CPGs and apply correction
    my_joints_angles = self.preprogrammed_steps.get_joint_angles(
        leg,
        self.cpg_network.curr_phases[i],
        self.cpg_network.curr_magnitudes[i],
    )
    my_joints_angles += net_correction * self.correction_vectors[leg[1]]
    joints_angles.append(my_joints_angles)

    # get adhesion on/off signal
    my_adhesion_onoff = self.preprogrammed_steps.get_adhesion_onoff(
        leg, self.cpg_network.curr_phases[i]
    )
    adhesion_onoff.append(my_adhesion_onoff)

...

This requires three helper methods:

def _stumbling_rule_check_condition(self, obs, leg):
    """Return True if the leg is stumbling, False otherwise."""
    # update stumbling correction amounts
    contact_forces = obs["contact_forces"][self.stumbling_sensors[leg], :]
    fly_orientation = obs["fly_orientation"]
    # force projection should be negative if against fly orientation
    force_proj = np.dot(contact_forces, fly_orientation)
    return (force_proj < self.stumbling_force_threshold).any()

def _get_net_correction(self, retraction_correction, stumbling_correction):
    """Retraction correction has priority."""
    if retraction_correction > 0:
        return retraction_correction
    return stumbling_correction

def _update_correction_amount(
    self, condition, curr_amount, correction_rates, viz_segment
):
    """Update correction amount and color code leg segment.

    Parameters
    ----------
    condition : bool
        Whether the correction condition is met.
    curr_amount : float
        Current correction amount.
    correction_rates : Tuple[float, float]
        Correction rates for increment and decrement.
    viz_segment : str
        Name of the segment to color code. If None, no color coding is
        done.

    Returns
    -------
    float
        Updated correction amount.
    """
    if condition:  # lift leg
        increment = correction_rates[0] * self.timestep
        new_amount = curr_amount + increment
        color = (0, 1, 0, 1)
    else:  # condition no longer met, lower leg
        decrement = correction_rates[1] * self.timestep
        new_amount = max(0, curr_amount - decrement)
        color = (1, 0, 0, 1)
    if viz_segment is not None:
        self.change_segment_color(viz_segment, color)
    return new_amount

Finally, we build the action dictionary (recall from our discussion on Gym spaces above — this is a composite Dict space) and call the step method of the parent NeuroMechFly class using it. This concludes the definition of our step method.

...

action = {
    "joints": np.array(np.concatenate(joints_angles)),
    "adhesion": np.array(adhesion_onoff).astype(int),
}
return super().step(action)

Let’s import this class and instantiate it:

 1from flygym.mujoco.examples.turning_controller import HybridTurningNMF
 2
 3run_time = 1
 4timestep = 1e-4
 5contact_sensor_placements = [
 6    f"{leg}{segment}"
 7    for leg in ["LF", "LM", "LH", "RF", "RM", "RH"]
 8    for segment in ["Tibia", "Tarsus1", "Tarsus2", "Tarsus3", "Tarsus4", "Tarsus5"]
 9]
10
11sim_params = Parameters(
12    timestep=1e-4,
13    render_mode="saved",
14    render_camera="Animat/camera_top",
15    render_playspeed=0.1,
16    enable_adhesion=True,
17    draw_adhesion=True,
18    actuator_kp=20,
19)
20
21nmf = HybridTurningNMF(
22    sim_params=sim_params,
23    contact_sensor_placements=contact_sensor_placements,
24    spawn_pos=(0, 0, 0.2),
25)

In fact, we can use Gymnasium’s env_checker utility to check if our HybridTurningNMF class fully complies with the Gym API. To do this, env_checker will reset our environment a few times with random parameters and step it with random actions. It will then check if the observations are as specified in the observation space definition. If no exception is raised, we are in good shape.

1check_env(nmf)
/opt/homebrew/Caskroom/miniforge/base/envs/flygym0.2/lib/python3.11/site-packages/gymnasium/utils/env_checker.py:247: UserWarning: WARN: For Box action spaces, we recommend using a symmetric and normalized space (range=[-1, 1] or [0, 1]). See https://stable-baselines3.readthedocs.io/en/master/guide/rl_tips.html for more information.
  logger.warn(
/opt/homebrew/Caskroom/miniforge/base/envs/flygym0.2/lib/python3.11/site-packages/gymnasium/utils/env_checker.py:225: UserWarning: WARN: A Box observation space minimum value is -infinity. This is probably too low.
  logger.warn(
/opt/homebrew/Caskroom/miniforge/base/envs/flygym0.2/lib/python3.11/site-packages/gymnasium/utils/env_checker.py:229: UserWarning: WARN: A Box observation space maximum value is -infinity. This is probably too high.
  logger.warn(
/opt/homebrew/Caskroom/miniforge/base/envs/flygym0.2/lib/python3.11/site-packages/gymnasium/utils/env_checker.py:321: UserWarning: WARN: Not able to test alternative render modes due to the environment not having a spec. Try instantialising the environment through gymnasium.make
  logger.warn(

Let’s run the simulation, applying a steady [1.2, 0.2] turn throughout. We will also record the magnitude of the CPGs over time.

1magnitude_hist = []
2obs, info = nmf.reset()
3for i in trange(int(run_time / nmf.sim_params.timestep)):
4    curr_time = i * nmf.sim_params.timestep
5    action = np.array([1.2, 0.2])
6    obs, reward, terminated, truncated, info = nmf.step(action)
7    nmf.render()
8    magnitude_hist.append(nmf.cpg_network.curr_magnitudes.copy())
100%|██████████| 10000/10000 [00:35<00:00, 285.38it/s]

Let’s visualize the time series of the CPG magnitudes. As expected, three CPGs converge to a faster step while the others converge to a smaller one.

1t = np.arange(0, run_time, nmf.sim_params.timestep)
2fig, ax = plt.subplots(1, 1, figsize=(4, 3), tight_layout=True)
3for ts in np.array(magnitude_hist).T:
4    ax.plot(t, ts)
5ax.set_xlabel("Time (s)")
6ax.set_ylabel("CPG magnitude")
7fig.savefig("./outputs/turning_cpg_magnitude.png")
https://github.com/NeLy-EPFL/_media/blob/main/flygym/turning_cpg_magnitude.png?raw=true

Finally, let’s take a look at the video:

1nmf.save_video("./outputs/hybrid_turning.mp4")