-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #100 from BharatSahAIyak/dev
Dev -> Main v0.4.5
- Loading branch information
Showing
59 changed files
with
676 additions
and
229 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,70 @@ | ||
# INTRODUCTION | ||
|
||
## Entities in the system | ||
|
||
### WORKFLOWS | ||
|
||
Every action taken by a user in autotune is mapped to a workflow. Autotune has two broad functions which is housed in the same place: `Synthetic Data Generation` and `Model Training`. These are built as two separate functions, with interoperability provided in autotune. | ||
Based on this, there are two types of workflows in autotune: `training` and `complete`. A complete workflow indicates that the entire process from the data generation to the training is being performed at autotune. A `training` workflow can be used to perform a subset of operations of a complete workflow. | ||
In training workflows, user can provide a HuggingFace dataset for training/fine tuning a model of a model. | ||
|
||
Autotune has the assumption that a given user will have only one workflow for training a given model type like `Text Classification`, `Named entity recognition`, etc. | ||
|
||
### CONFIG | ||
|
||
Configs are re-usable components which provides metadata and various other fixed aspects of a workflow. | ||
|
||
Overall config items which can be stored are: | ||
|
||
- temperature: OpenAI temperature used in dataset generation | ||
- system_prompt: System prompt which is passed to OpenAI API. | ||
- user_prompt_template: A template with replaceable values according to workflow needs. | ||
- schema_example: A sample JSON which we want the generated data to follow. We can create dynamic models of any structure we like, with validation using dynamically created pydantic models | ||
|
||
### TASKS | ||
|
||
### TRAINING | ||
|
||
## Development Journey | ||
|
||
## Models Supported | ||
|
||
- Text Classification | ||
- Colbert training | ||
- Force Alignment | ||
|
||
# SETUP | ||
|
||
## API specifications | ||
|
||
There are two versions of the APIs, with the core functionality accross both the APIs the same | ||
|
||
### POST /v1/workflow/config | ||
|
||
- REQUEST: | ||
|
||
- RESPONSE: | ||
|
||
### POST /v1/workflow/create | ||
|
||
- REQUEST: | ||
|
||
- RESPONSE: | ||
|
||
### POST /v1/workflow/iterate/<UUID> | ||
|
||
- REQUEST: | ||
|
||
- RESPONSE: | ||
|
||
### POST /v1/workflow/generate/<UUID> | ||
|
||
- REQUEST: | ||
|
||
- RESPONSE: | ||
|
||
### POST /v1/workflow/status/<WORKFLOW_ID> | ||
|
||
- REQUEST: | ||
|
||
- RESPONSE: |
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.