Practice: intro to classes#

Let us suppose we have a set of weather stations that do measurements of wind speed and temperature in a weather station (for example in Paris). We need to store these measurements in a clear way so that computing statistics (maximum wind, average temperature…) is easy and not error prone. This chapter shows different ways of storing the data, its advantages and disadvantages.

The basic way: only with lists#

Exercise 21 (A list of lists)

A basic representation of our Paris weather station will be a unique list of lists. Write one list with two elements containing the wind values and temperature values. Find the values of the maximum temperature and wind.

wind_values = [10, 0, 20, 30, 20, 4]
temperature_values = [1, 5, 1, -1, -1, 3]

Comments on this solution#

Many problems:

  • if the number of measurements increases (e.g. having rainfall, humidity, …) the previous indexing will not be valid (what will paris[5] represent? wind, temperature, …, ?)

  • Code analysis is not (that) straightforward

More complex structures: mixing dicts and lists#

Exercise 22 (A dict of lists)

Instead of storing everything in lists, use a dictionnary to store the different types of measurements

Comments#

  • Pro

    • More readable code (reading paris["temperature"] is clearer than paris[1]).

    • Less error prone code (i.e. using words as keys allow to not use index numbers that are easily mistaken and lead to code that is hard to read and debug)

  • Con

    • The code to compute the final result is not very readable

Improve database: add functions#

Exercise 23 (Improve the dict weather station)

Write a function that returns the maximum temperature and another one that returns the index of the maximum temperature. It should work on the dict you wrote in the previous exercise.

Comments#

  • Pro:

    • Adding functions leads to a code that is easier to read, hence easier to debug.

    • Testing functions can be done separately from the rest of the code.

    • The computation done on the second part depends upon the functions (i.e it depends on the function definitions not their implementations).

    • Adding function allows to reuse code: computing the max temperature is something one could want to do in other places.

  • Con

    • We rely on the fact that the dictionaries have been built correctly (for example wind and temperature arrays have the same length).

Continue improving: build a init function#

Exercise 24 (Build an init function)

Define a function that builds the station (delegate the generation of the station dictionary to a function). The init function should test if the two set of measurements have the same length, and stop the execution if not.

Comments#

  • If the dedicated function build_station is used, the returned dictionary is well structured.

  • If one changes build_station, only max_temp and arg_max_temp have to be changed accordingly

  • We use a list comprehension to be able to have parameters wind and temp provided by any ordered iterable (e.g. see test_build_station_with_iterable wtih range)

  • BUT if we have a new kind of station, i.e. that holds only wind and humidity, we want to avoid to be able to use max_temp with it.

Last improvement: using a class#

We would like to “embed” the max_temp and the arg_max_temp in the “dictionary station” in order to address the last point.

And here comes object-oriented programming !

A class defines a template used for building object. In our example, the class (named WeatherStation) defines the specifications of what is a weather station (i.e, a weather station should contain an array for wind speeds, named “wind”, and an array for temperatures, named “temp”). paris should now be an object that answers to these specifications. Is is called an instance of the class WeatherStation.

When defining the class, we need to define how to initialize the object (special “function” __init__).

Exercise 25 (Build the class)

We provide a skeleton for the class. Take the code defined in the previous exercises and fill the holes

class WeatherStation:
    """A weather station that holds wind and temperature

    :param wind: any ordered iterable
    :param temperature: any ordered iterable

    wind and temperature must have the same length.

    """

    def __init__(self, wind, temperature):
        """initialize the weather station.
        Precondition: wind and temperature must have the same length.
                      ValueError is raised if this is not the case
        :param wind: any ordered iterable
        :param temperature: any ordered iterable"""
        pass

    def max_temp(self):
        """returns the maximum temperature recorded in the station"""
        pass

    def arg_max_temp(self):
        """returns the index of (one of the) maximum temperature recorded in the station"""
        pass

Comments#

  • The max_temp and the arg_max_temp are now part of the class WeatherStation. Functions attached to classes are named methods. Similarly, wind and temp lists are also now part this class. Variables attached to classes are named members or attributes.

  • if max_temp method is called in many places, we can improve it by caching the result. This will not affect code the uses the class.

  • arg_max_temp method should be rewritten as we implicitly check equality of floats.

An object (here paris) thus contains both attributes (holding data for example) and methods to access and/or process the data.

Exercise 26 (Try to code with class)

  • Add a method (perceived_temp) that takes as input a temperature and wind and return the perceived temperature, i.e. taking into account the wind chill effect.

  • Modify max_temp and arg_max_temp so that they take an additional optional boolean parameter (e.g. perceived default to False). If perceived is False, the methods have the same behaviour as before. If perceived is True, the temperatures to process are the perceived temperatures.

Comments#

  • The wind array was changed to have different maximum temperatures for the air and perceived temperatures: for air temperatures, the max is 5°C (with a wind speed 50 km/h). For perceived temperatures, the max is 3°C (as the wind speed is 0).

  • It was a choice to set the apparent/perceived temperature to the air temperature if the wind speed is 0 so the tests were written with this in mind. Testing such choices allows to have clear inputs/outputs.

  • isinstance allows to test the type of an object (in this case, we test if apparent_temps is a list)

  • When testing boolean in if structures: use if perceived: rather than if perceived == True:. It is equivalent but clearer and shorter !

Coming next: inheritance#

What if we now have a weather station that also measure humidity ?

Do we need to rewrite everything ?

What if we rewrite everything and we find a bug ?

Here comes inheritance