Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor of test suite and addition of explicit validation data sets #32

Merged
merged 18 commits into from
Jul 27, 2018

Conversation

matthewcarbone
Copy link
Collaborator

Major overhaul of the testing suite:

  • Move things out of the single test_script.py and into test directory.
  • Explicit unit tests on Scan.
  • Needs more work: need to explicitly test every function individually.

Also, add the explicit validation data set option

  • Add the option to Scan to specify x_val and y_val.
  • Overrides the val_split option.

Let me know what you think @mikkokotila. Hope I didn't do too much at once here...

matthewcarbone and others added 18 commits July 23, 2018 00:05
Add docstrings to validation_split() and random_shuffle(). Also,
add capability to seed the random shuffle generator so taht results
may be reproducible, at least in terms of the random shuffling of
the train/cross-validation data.
To allow for a user to potentially augment their training data but
not their validation data (and it should be noted that nobody should
ever augment first then randomize then split, else major bias
problems), implement an option to explicitly specify the validation
dataset.

Also make necessary changes to validation_split to account for this,
and make a few QOL edits to the testing suite.
Clean up completely. Make the following changes:
- Move all tests into test/ directory
- test_script.py still calls all the same unit checks as before
- Move test models (iris and cervical cancer) to
  talos/model/examples.py
Notably, bugfix an error in Scan where the attributes x_val and y_val
were not being defined.
Appears that fmeasure was changed to fmeasure_acc in a previous
commit.
@pep8speaks
Copy link

Hello @x94carbone! Thanks for submitting the PR.

  • In the file setup.py, following are the PEP8 issues :

Line 94:1: E124 closing bracket does not match visual indentation

Line 1:1: W391 blank line at end of file

@coveralls
Copy link

Pull Request Test Coverage Report for Build 103

  • 43 of 44 (97.73%) changed or added relevant lines in 3 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+0.4%) to 88.571%

Changes Missing Coverage Covered Lines Changed/Added Lines %
talos/utils/validation_split.py 11 12 91.67%
Totals Coverage Status
Change from base Build 97: 0.4%
Covered Lines: 682
Relevant Lines: 770

💛 - Coveralls

@mikkokotila
Copy link
Contributor

This is amazing! Thanks a lot for great work 👍

@matthewcarbone
Copy link
Collaborator Author

My pleasure! Got another one coming in a sec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants