__pycache__/

*.py[cod]

env/

build/

develop-eggs/

dist/

downloads/

eggs/

.eggs/

lib/

lib64/

parts/

sdist/

var/

wheels/

*.egg-info/

htmlcov/

.tox/

.hypothesis/

instance/

docs/_build/

target/

*/.ipynb_checkpoints

venv/

ENV/

/site

.mypy_cache/

*/pickle_jar/

docs/notebooks/pickle_jar/

.idea/

language: python

sudo: required

cache:

directories:

- $HOME/.theano

- $HOME/miniconda2

- $HOME/miniconda3

addons:

apt_packages:

- pandoc

before_install:

- . ./scripts/install_miniconda.sh

- sh -e /etc/init.d/xvfb start

- export DISPLAY=":99.0"

- export MKL_THREADING_LAYER=GNU

install:

- . ./scripts/create_testenv.sh

- pip install coveralls travis-sphinx==2.0.0

env:

- PYTHON_VERSION=2.7 FLOATX='float32' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=2.7 FLOATX='float32' RUN_PYLINT="true" TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=2.7 FLOATX='float32' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=2.7 FLOATX='float32' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=2.7 FLOATX='float64' TESTCMD="--durations=10"

- PYTHON_VERSION=2.7 FLOATX='float64' RUN_PYLINT="true" TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=2.7 FLOATX='float64' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=3.6 FLOATX='float64' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=3.6 FLOATX='float64' TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=3.6 FLOATX='float64' BUILD_DOCS="true" TESTCMD="--durations=10 --cov-append"

- PYTHON_VERSION=3.6 FLOATX='float64' TESTCMD="--durations=10 --cov-append pmlearn/tests/test_logistic.py pmlearn/tests/test_base.py pmlearn/tests/test_base1.py pmlearn/tests/test_gpr.py"

script:

- . ./scripts/test.sh $TESTCMD

- . ./scripts/confirm_mpl_optional.sh

after_success:

- coveralls

Daniel Emaasit <demaasit@haystax.com>, <daniel.emaasit@gmail.com>

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/).

- First version of the library

- Gaussian process Regressor

- Student's t process Regressor

- Sparse Gaussian process Regressor

- Documentation

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.

Examples of behavior that contributes to creating a positive environment include:

* Using welcoming and inclusive language

* Being respectful of differing viewpoints and experiences

* Gracefully accepting constructive criticism

* Focusing on what is best for the community

* Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

* The use of sexualized language or imagery and unwelcome sexual attention or advances

* Trolling, insulting/derogatory comments, and personal or political attacks

* Public or private harassment

* Publishing others' private information, such as a physical or electronic address, without explicit permission

* Other conduct which could reasonably be considered inappropriate in a professional setting

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.

This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at demaasit@haystax.com. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.

This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]

[homepage]: http://contributor-covenant.org

[version]: http://contributor-covenant.org/version/1/4/

Thank you for considering contributing to ``pymc-learn``! This project is intended to be a space where anyone can share models they've built.

Please read these guidelines before submitting anything to the project. As of the first release, I'm the only person working on this project so respecting these guidelines will help me get back to you more quickly.

Some ways to contribute:

- Open an issue on the `Github Issue Tracker <https://github.com/pymc-learn/pymc-learn/issues>`__. (Please check that it has not already been reported or addressed in a PR.)

- Improve the docs!

- Add a new machine-learning model. Please follow the guidelines below.

- Add/change existing functionality in the base function classes for ML.

- Something I haven't thought of?

Pull/Merge Requests

To create a Pull Request against this library, please fork the project and work from there.

Steps

1. Fork the project via the Fork button on Github

2. Clone the repo to your local disk, and add the base repository as a remote.

.. code-block:: bash

3. Create a new branch for your PR.

.. code-block:: bash

Always use a ``feature`` branch. It's good practice to never routinely work on the ``master`` branch.

4. Install requirements (probably in a virtual environment)

.. code-block:: bash

NOTE: On Windows, in your Anaconda Prompt, run ``activate myenv``.

5. Develop your feature. Add changed files using ``git add`` and then ``git commit`` files:

.. code-block:: bash

to record your changes locally. After committing, it is a good idea to sync with the base repository

in case there have been any changes:

.. code-block:: bash

Then push the changes to your Gitlab account with:

.. code-block:: bash

6. Submit a Pull Request! Go to the Github web page of your fork of the ``pymc-learn`` repo. Click the 'Create pull request' button

to send your changes to the project maintainers for review. This will send an email to the committers.

Pull Request Checklist

- Ensure your code has followed the Style Guidelines below

- Make sure you have written unittests where appropriate

- Make sure the unittests pass

.. code-block:: bash

NOTE: On Windows, in your Anaconda Prompt, run ``activate myenv``.

- Update the docs where appropriate. You can rebuild them with the commands below.

.. code-block:: bash

- Update the CHANGELOG

Style Guidelines

For the most part, this library follows PEP8 with a couple of exceptions.

Notes:

- Indent with 4 spaces

- Lines can be 120 characters long

- Docstrings should be written as numpy docstrings

- Your code should be Python 3 compatible

- When in doubt, follow the style of the existing code

Copyright (c) 2019 Pymc-learn Developers

All rights reserved.

Redistribution and use in source and binary forms, with or without modification,

are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,

this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice,

this list of conditions and the following disclaimer in the documentation

and/or other materials provided with the distribution.

3. Neither the name of Pymc-learn nor the names of any contributors may be used to

endorse or promote products derived from this software without specific prior

written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"

AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE

IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE

ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE

LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR

CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF

SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS

INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN

CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)

ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF

THE POSSIBILITY OF SUCH DAMAGE.

include AUTHORS.txt LICENSE README.rst