Draft pr1

[1andrin]

Problem

Increase number of available scores, fix issues in existing scores, extend functionality of datasets.py to include generation of data with known propensites, simplify the running of experiments. Facilitate reproducible experiments.

Proposed changes

Extended scoring.py with the new BITE metrics, updated the forbenius norm score, updated policy risk, updated probabilistic erupt. Added a method to create data with known propensities in datasets.py. Created the experiment_runner.py file to facilitate simplified experiment runs and added instructional readme. Added a set of pre-made data sets for each scenario to allow for reproducible experiments.

Types of changes

What types of changes does your code introduce to causaltune?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

• I have read the CONTRIBUTING doc
• Description above provides context of the change
• I have added tests that prove my fix is effective or that my feature works
• Unit tests for changes (not needed for documentation changes)
• Bumping version in setup.py is an individual PR and not mixed with feature or bugfix PRs
• Commits follow "How to write a good git commit message"
• Relevant documentation is updated including usage instructions