GPTkeras
GPTkeras aims to solve the struggles of guessing model configurations and hyperparameters when developing machine learning projects. Instead of manually tuning architectures and settings, you simply provide your training data (x and y), and this library leverages large language models (LLMs) specifically ChatGPT to automatically generate suitable layers and hyperparameters for your dataset.
The workflow is as follows:
- You provide your training data.
- The library uses ChatGPT to draft a Keras model architecture and select hyperparameters tailored to your data.
- It runs a training session and evaluates the results.
- The training results are then passed back to the LLM, which attempts to further improve the model configuration in subsequent iterations.
Another major challenge in machine learning experimentation is tracking changes to models and understanding how those changes affect results. GPTkeras addresses this by using the LLM to log and manage conversational context, so you can see how each modification impacts performance over time.
This toolkit wraps the OpenAI Chat Completions API and provides helpers for drafting model architectures, managing experiments, and logging conversational context when iterating on training runs.
Installation
pip install GPTkeras
Quick start
from GPTkeras import GPTkeras
model = GPTkeras(train_x, train_y, api_key="sk-...")
model.fit(max_iterations=3)
Documentation
GPTkeras Arguments
GPTkeras(
train_x, # Required. Training input data (numpy array or tensor)
train_y, # Required. Training target data (numpy array or tensor)
api_key=None, # Required. OpenAI API key for LLM access
model="gpt-4o-mini", # Optional. OpenAI model name (default: "gpt-4o-mini")
history_path="chat_history.jsonl", # Optional. Path to log conversational/model history (default: "chat_history.jsonl")
continue_from_history=False, # Optional. If True, resumes conversation/model history from previous runs (default: False)
)
Contributing
Contributions, suggestions, and bug reports are welcome! Feel free to open issues or submit pull requests to help improve GPTkeras.
Metadata
Release files for GPTkeras 0.0.2
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 | Actions |
|---|---|---|---|---|
| gptkeras-0.0.2.tar.gz | 6.8 kB | Without provenance | Details for gptkeras-0.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gptkeras-0.0.2-py3-none-any.whl | Python 3 | none | any | Details for gptkeras-0.0.2-py3-none-any.whl |
Total release size: 13.8 kB
Release files / gptkeras-0.0.2.tar.gz
| Download URL | gptkeras-0.0.2.tar.gz |
|---|---|
| Size | 6.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2fea5fed73459b9af7c175395ff2b2fcf727f0c75ce7b8f4e110814f4f3faac5
|
|
BLAKE2b-256 checksum How to use checksums |
44a8f122d6d57f943b9f42dc07593979b554b34d27967723c012701fa8f6957b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / gptkeras-0.0.2-py3-none-any.whl
| Download URL | gptkeras-0.0.2-py3-none-any.whl |
|---|---|
| Size | 7.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
73b1bdb3b9d055eaf030a2a1f4b66916a4d669c84f5e457a00254d9199610162
|
|
BLAKE2b-256 checksum How to use checksums |
2b16090bf4c7f024342effe57fb03c83490fd2a287c988740617e8be4b822dc9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for GPTkeras 0.0.2
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.