Tips and tricks¶

Preventing code duplication¶

As much as possible, it’s good to avoid copy-pasting the same code in multiple places. Although it sometimes takes a bit of thinking to figure out how to avoid copy-pasting code, you will see that having your code in only one place usually saves you a lot of effort later when you need to change the design of your code or fix bugs.

Below are some techniques to achieve code reuse.

Don’t make multiple copies of your app¶

If possible, you should avoid copying an app’s folder to make a slightly different version, because then you have duplicated code that is harder to maintain.

If you need multiple rounds, set num_rounds. If you need slightly different versions (e.g. different treatments), then you should use the techniques described in Treatments, such as making 2 session configs that have a different 'treatment' parameter, and then checking for self.session.config['treatment'] in your app’s code.

Templates: prevent code duplication by using a base template¶

If you are copy-pasting the same JavaScript or CSS to multiple templates, you should instead put it in one of the following blocks in a base template:

{% block global_styles %}
{% block global_scripts %}
{% block app_styles %}
{% block app_scripts %}

Prevent duplicate pages by using multiple rounds¶

If you have many many pages that are almost the same, consider just having 1 page and looping it for multiple rounds. One sign that your code can be simplified is if it looks something like this:

# [pages 1 through 7....]

class Decision8(Page):
    form_model = 'player'
    form_fields = ['decision8']

class Decision9(Page):
    form_model = 'player'
    form_fields = ['decision9']

# etc...

See the quiz or real effort sample games for examples of how to just have 1 page that gets looped over many rounds, varying the question that gets displayed with each round.

pages.py: prevent code duplication by moving code to your models¶

You should try to move as much code as possible into your Player/Group/Subsession. In Django, it’s generally recommended to have “thick models” and “thin pages”.

Example 1: is_displayed¶

For example, let’s say that your page classes all repeat some of the code. For example, you use is_displayed to skip the rest of the app once a certain participant var is set:

class Page1(Page):
    def is_displayed(self):
        return self.participant.vars.get('consented') and not self.participant.vars.get('finished')

class Page2(Page):
    def is_displayed(self):
        return self.participant.vars.get('consented') and not self.participant.vars.get('finished')

class Page3(Page):
    def is_displayed(self):
        if self.participant.vars.get('consented') and not self.participant.vars.get('finished'):
            if self.player.id_in_group == 1:
                return True
        return False

page_sequence = [
    Page1,
    Page2,
    Page3,
]

You can eliminate this repetition by moving the is_displayed code into the Player model:

class Player(BasePlayer):
    def is_playing(self):
        pvars = self.participant.vars
        return pvars.get('consented') and not pvars.get('finished')

Then in your pages:

class Page1(Page):
    def is_displayed(self):
        return self.player.is_playing()

class Page2(Page):
    def is_displayed(self):
        return self.player.is_playing()

class Page3(Page):
    def is_displayed(self):
        return self.player.is_playing() and self.player.id_in_group == 1

page_sequence = [
    Page1,
    Page2,
    Page3,
]

Example 2: vars_for_template¶

Let’s say you’ve got the following code (note that Page3 passes extra variables d and e):

class Page1(Page):
    def vars_for_template(self):
        return dict(a=1, b=2, c=3)

class Page2(Page):
    def vars_for_template(self):
        return dict(a=1, b=2, c=3)

class Page3(Page):
    def vars_for_template(self):
        return dict(a=1, b=2, c=3, d=4, e=5)

You can simplify this by making a method on your Player model:

class Player(BasePlayer):
    def vars_for_template(self):
        return dict(a=1, b=2, c=3)

Then in your pages:

class Page1(Page):
    def vars_for_template(self):
        return self.player.vars_for_template()

class Page2(Page):
    def vars_for_template(self):
        return self.player.vars_for_template()

class Page3(Page):
    def vars_for_template(self):
        return dict(self.player.vars_for_template(), d=4, e=5)

Improving code performance¶

You should avoid redundant use of get_players(), get_player_by_id(), in_*_rounds(), get_others_in_group(), or any other methods that return a player or list of players. These methods all require a database query, which can be slow.

For example, this code has a redundant query because it asks the database 5 times for the exact same player:

class MyPage(Page):
    def vars_for_template(self):
        return dict(
            a=self.player.in_round(1).a,
            b=self.player.in_round(1).b,
            c=self.player.in_round(1).c,
            d=self.player.in_round(1).d,
            e=self.player.in_round(1).e
        )

It should be simplified to this:

class MyPage(Page):
    def vars_for_template(self):
        round_1_player = self.player.in_round(1)
        return dict(
            a=round_1_player.a,
            b=round_1_player.b,
            c=round_1_player.c,
            d=round_1_player.d,
            e=round_1_player.e
        )

As an added benefit, this usually makes the code more readable.

Use BooleanField instead of StringField, where possible¶

Many StringFields should be broken down into BooleanFields, especially if they only have 2 distinct values.

Suppose you have a field called treatment:

treatment = models.StringField()

And let’s say treatment it can only have 4 different values:

high_income_high_tax
high_income_low_tax
low_income_high_tax
low_income_low_tax

In your pages, you might use it like this:

class HighIncome(Page):
    def is_displayed(self):
        return self.player.treatment == 'high_income_high_tax' or self.player.treatment == 'high_income_low_tax'

class HighTax(Page):
    def is_displayed(self):
        return self.player.treatment == 'high_income_high_tax' or self.player.treatment == 'low_income_high_tax'

It would be much better to break this to 2 separate BooleanFields:

high_income = models.BooleanField()
high_tax = models.BooleanField()

Then your pages could be simplified to:

class HighIncome(Page):
    def is_displayed(self):
        return self.player.high_income

class HighTax(Page):
    def is_displayed(self):
        return self.player.high_tax