Git Product home page Git Product logo

bachelorproject's Introduction

bachelorproject's People

Contributors

surya-sankagiri avatar thosam1 avatar

Stargazers

 avatar  avatar  avatar  avatar

Watchers

 avatar

Forkers

hyrros

bachelorproject's Issues

Interpreting plots

Whenever you have a plot, write a brief description about what is the main insight from the plot. If there is no insight, there is no need to plot it!

Strategy 4 bugs

The times at which you eliminate arms, and the probability estimates seem correct. But the plots below show linear regret, which seems wrong

Bugs in epsilon-greedy?

why is the plot for number of times suboptimal arm being played increasing linearly? is a suboptimal arm being played every time?

regret plot is also piecewise linear. I would have expected it to be a bit more smooth.

Plots for explore-then-commit

Draw vertical dashed lines to show the exploration stage of each arm.

Correct the title of the regret plot; it says epsilon greedy, but it should be explore-then-commit. The same issue is there in strategy 2 as well.

Normalize histogram plots

The histogram plots will give more information if each time you divide by total number of plays., so that each value is between 0 and 1. Maybe you can also plot the histogram of the true probabilities just beside, so as to get an estimate.

Clarify strategy 2

Can you give more details on explore-then-exploit by elimination? What are the parameters you give as input to the algorithm?
What happens in each round? Perhaps you could reuse your functions from strategy 1?

Are you eliminating the arms in the same order as their probability of giving a reward? This is what I meant by writing some explanation below your plots in a previous issue.

In the plot for number of wins per arm as a function of nth play, just cut of the plots for the arms you stop playing, instead of making them continue out flat. perhaps you can replace the remaining numbers by None, and the plot will automatically correct for it.

Restructuring code

your current ipynb is rather big, it's a bit difficult to navigate.
you can create different ipy notebooks for different weeks tasks.
common functions can be put in .py files that are imported into the notebook.
The main code and the plots can be kept in the notebook.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.