This week I learnt — how to add “$” to ticks on matplotlib graphs

Please examine Kaggle’s Python exercise 7 to try this yourself.

This week I completed Kaggle’s python exercise 7. In that exercise, there was a simple but interesting challenge of adding “$” to the y-axis ticks on a matplotlib graph. And this post is my documentation of my process.


Here’s the question from Kaggle:

After completing the exercises on lists and tuples, Jimmy noticed that, according to his estimate_average_slot_payout function, the slot machines at the Learn Python Casino are actually rigged against the house, and are profitable to play in the long run.

Starting with $200 in his pocket, Jimmy has played the slots 500 times, recording his new balance in a list after each spin. He used Python’s matplotlib library to make a graph of his balance over time:


The tasks were to start the y-axis from 0, label the y-axis and add a title to the graph.

All three were easily done by adding three functions found in the directory:


The question had a challenge: to add “$” to the y-axis ticks.
Seems simple enough. Or so I thought as I looked through the directory of the graph function. I identified one useful method— set_yticks.

Experimenting with it gave me error after error. Frustrated at my lack of knowledge, I turned to the internet and found matplotlib documentation for dollar ticks. Here’s the code:

Looks like it has what I need. I isolated the line of code responsible for the dollar ticks with cents:

Add that to the code in Kaggle:

Success! But that’s not the end. I need to compare it with Kaggle’s solution.

Kaggle’s solution

Being through, I deactivated my solution and ran Kaggle’s solution.

Looks like there are two issues with Kaggle’s solution. Firstly, the y-axis has lost the two decimal places. Secondly, what is the implication of the user warning and should I be concerned?


The first issue was not really an issue for this problem, but I wanted to know what caused the decimal points to disappear. The steps to solve it was simple — isolate the lines of code from both solutions and compare them. The difference was the formatting argument:

Scanning from left to right. The dollar sign is needed for “$” in the tick. The text in {} formats the ticker value. x is the ticker value (in our case is 50, 100, 150, 200, 250, 300). So the code for the two decimal position is — :1.2f. Kaggle’s solution did not have x as the argument is passed into each value of the ticker later in the code.

Hence the modified Kaggle solution would be:

And the complete solution is:

Onwards to solve the second issue: the user warning — FixedFormatter should only be used together with FixedLocator

I did a little digging on the internet and found another useful tutorial on Link here

This tutorial is lengthy as it covers many types of tick formatting. I highly recommend reading it. Isolating the section related to the user warning (Setup code not shown here, but can be found in the source link):

The tutorial indicates both FixedFormatter and FixedLocator should be used together, but not a must. So it is not an issue to fix now. Rather, I noted down the potential implication in the code so I know to use FixedLocator should the y-axis label appear at non-standard locations.


This was a fun and simple exercise. I spent more time documenting than solving it as I had to backtrack and take screenshots and copy codes when writing this. Aiming to improve my documentation process.

I'm starting out in the world of Data Science. Working to be a qualified and employed Data Analyst. Follow me on my journey!

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store