AutoDoc
This project was automatically generated using the LINCC-Frameworks python-project-template. For more information about the project template see the documentation.
Dev Guide - Getting Started
Before installing any dependencies or writing code, it's a great idea to create a
virtual environment. We recommend using conda to manage virtual
environments. If you have conda installed locally, you can run the following to
create and activate a new environment.
>> conda create env -n <env_name> python=3.8
>> conda activate <env_name>
Once you have created a new environment, you can install this project for local development using the following commands:
>> pip install -e .'[dev,pipelines]'
>> pre-commit install
>> conda install pandoc
Notes:
- The single quotes around
'[dev]'may not be required for your operating system. - Look at
pyproject.tomlfor other optional dependencies, e.g. you can dopip install -e ."[dev,pipelines,cuda]"if you want to use CUDA. pre-commit installwill initialize pre-commit for this local repository, so that a set of tests will be run prior to completing a local commit. For more information, see the Python Project Template documentation on pre-commit- Install
pandocallows you to verify that automatic rendering of Jupyter notebooks into documentation for ReadTheDocs works as expected. For more information, see the Python Project Template documentation on Sphinx and Python Notebooks
Running AzureML pipelines
This repo contains the evaluation and training pipelines for AutoDoc.
Prerequisites
Add the ML extension:
az extension add --name ml
Configure the CLI:
az login
az account set --subscription "<your subscription name>"
az configure --defaults workspace=<aml workspace> group=<resource group> location=<location, e.g. westus3>
Running jobs
Prediction
az ml job create -f azureml/eval.yml --set display_name="Test prediction job" --set environment_variables.HF_TOKEN=<your huggingface token> --web
Notes:
--namewill set the mlflow run id--display_namebecomes the name in the experiment dashboard--webargument will pop-up a browser window for tracking the job.- The
HF_TOKENis required for gated repos, which need authentication
Uploading data
Example:
az storage blob upload --account-name <account> --container <container>> --file data/data.jsonl -n data/sweetpea/data.jsonl
Metadata
Release files for autora-doc 0.0.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| autora_doc-0.0.5.tar.gz | 11.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| autora_doc-0.0.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 24.2 kB
Release files / autora_doc-0.0.5.tar.gz
| Download URL | autora_doc-0.0.5.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d7ff2a350547ec1f965ff5f0174d07481b238287d3f354c8fc26070d4a1a1648
|
|
BLAKE2b-256 checksum How to use checksums |
d6ef8a6aa5f306fbe9168321781af54ff85d43eb3d447f01fb27ef71ab326a40
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Release files / autora_doc-0.0.5-py3-none-any.whl
| Download URL | autora_doc-0.0.5-py3-none-any.whl |
|---|---|
| Size | 13.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
09dd76dfdec153b12464bf383cd356340c8fcd9ef96af6185b1100bcbcfeea67
|
|
BLAKE2b-256 checksum How to use checksums |
4ab9a3baae7446f71b2071341355a140d31f5c54ad154d425f28fd503d50d47f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/4.0.2 CPython/3.11.8
|
Security for autora-doc 0.0.5
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.