autora-experimentalist-poppernet 1.0.0a0

Pooler that generates samples for independent variables by maximizing the loss

AutoRA Template

Quickstart Guide

Install this in an environment using your chosen package manager. In this example we are using virtualenv

Install:

• python (3.8 or greater): https://www.python.org/downloads/
• virtualenv: https://virtualenv.pypa.io/en/latest/installation.html

Create a new virtual environment:

virtualenv venv

Activate it:

source venv/bin/activate

Use pip install to install the current project (".") in editable mode (-e) with dev-dependencies ([dev]):

pip install -e ".[dev]"

Add your contribution

Your autora-subpackage should include (1) your code implementing in the respective folder of src/autora/*, (2) unit tests for your contribution in the tests folder, and (3) respective documentation. (4) Update the README.md file (5) Delete all folders in src/autora that don't contain your contribution

Adding your code implementation

Add your code implementation to src/autora/theorist, src/autora/experimentalist or src/autora/experiment_runner. You can create new categories if none of them seems fitting.

Adding tests

You should also add tests. These can be doctests or as test cases in tests/test_your_contribution_name.py.

Adding documentation

• You may document your contribution in docs/index.md. You can also add new pages in the docs folder
• Update the mkdocs.yml file to reflect structure of the documentation. For example, you can add new pages or delete pages that you deleted from the docs folder.

Add new dependencies

In pyproject.toml add the new dependencies under dependencies

Install the added dependencies

pip install -e ".[dev]"

Publishing the package

Update the metadata under project in the pyproject.toml file to include name, description, author-name, author-email and version. Also, update the URL for the repository under project.urls.

• Follow the guide here: https://packaging.python.org/en/latest/tutorials/packaging-projects/

Build the package using:

python -m build

Publish the package to PyPI using twine:

twine upload dist/*

Publishing with GitHub actions

To automate the publishing process for your package, you can use a GitHub action instead of Twine:

• Add the GitHub action to the .github/workflows directory: For example, you can use the default publishing action:
  • Navigate to the actions on the GitHub website of your repository.
  • Search for the Publish Python Package action and add it to your project
• Create a new release: Click on create new release on the GitHub website of your repository.
• Choose a tag (this is the version number of the release. If you didn't set up dynamic versioning it should match the version in the pyproject.toml file)
• Generate release notes automatically by clicking generate release, which adds the markdown of the merged pull requests and the contributors.
• If this is a pre-release check the box set as pre-release
• Click on publish release

Dynamic versioning

To automatically generate the version number for each release, you can use dynamic versioning instead of updating the version number manually. To set this up, you need to alter the pyproject.toml file:

• Replace version = "..." with dynamic = ["version"] under project
• Replace the build-system section with the following:

[build-system]
requires = ["setuptools", "setuptools_scm"]
build-backend = "setuptools.build_meta"

• Add a new section to the pyproject.toml file:

[tool.setuptools_scm]

Dynamic versioning: Publishing using twine

If you are using dynamic versioning with Twine, follow these steps to publish your package:

• Commit all of your changes.
• Tag the commit: Create an annotated Git tag at the commit you want to release. This is typically the most recent commit on your main branch. For example, you can run git tag -a 1.0.0a to create a tag named "1.0.0a" at the current commit.
• Build and release the package using Twine as described in the above section.

Dynamic versioning: Publishing via GitHub actions

You can use dynamic versioning with the GitHub action described in the previous section. The workflow remains the same, but you don't have to update the version in the pyproject.toml file.

Workflows

...