forked from Significant-Gravitas/AutoGPT
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
windows docs make workspace if not there (#25)
* windows docs make workspace if not there * small fixes
- Loading branch information
1 parent
ef5c4f8
commit b8c7c05
Showing
2 changed files
with
24 additions
and
22 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -13,54 +13,53 @@ documented. | |
|
||
Clone the repo with: | ||
|
||
`git clone [email protected]:Significant-Gravitas/Auto-GPT-Benchmarks.git` | ||
`cd Auto-GPT-Benchmarks` | ||
git clone [email protected]:Significant-Gravitas/Auto-GPT-Benchmarks.git | ||
cd Auto-GPT-Benchmarks | ||
|
||
Create a venv with | ||
|
||
`python3.9 -m venv venv` | ||
python3.9 -m venv venv | ||
|
||
|
||
Activate it with | ||
On MaxOS/Linux Activate it with | ||
|
||
`source venv/bin/activate` | ||
source venv/bin/activate | ||
|
||
On Windows: | ||
|
||
venv/scripts/activate | ||
|
||
Install the requirements with: | ||
|
||
`pip install -r requirements.txt` | ||
pip install -r requirements.txt | ||
|
||
If you haven't already clone the AutoGPT repo somewhere else on your machine. | ||
DO NOT CLONE IT INTO A SUBDIR OF THIS REPO. | ||
|
||
`cd somewhere/else` | ||
`git clone [email protected]:Significant-Gravitas/Auto-GPT.git` | ||
cd somewhere/else | ||
git clone [email protected]:Significant-Gravitas/Auto-GPT.git | ||
cd Auto-GPT | ||
git checkout stable # Or the branch you want to benchmark | ||
|
||
You will need to update the .env file in the Auto-GPT repo to have your OpenAI api key. The file in question is at: | ||
You will need to update the .env file in the Auto-GPT repo to have your OpenAI api key. The file in question is at. This should becopied from the .env.template as described in the Auto-GPT README.md | ||
|
||
`Auto-GPT/.env` | ||
Auto-GPT/.env | ||
|
||
Finally, we assume you have a docker container built from the Dockerfile in the Auto-GPT repo. | ||
|
||
Build this with: | ||
|
||
`cd Auto-GPT` | ||
`docker build -t autogpt .` | ||
|
||
If you want to run with redis as your memory system, you can stand up a redis image in the AutoGPT repo with | ||
|
||
`docker compose up` | ||
|
||
Then you will need to adjust some variables in your .env file to use the redis memory backend. | ||
See the AutoGPT docs on how to do that. | ||
cd Auto-GPT | ||
docker build -t autogpt . | ||
|
||
Run your first eval with: | ||
|
||
`cd Auto-GPT-Benchmarks` | ||
`python3 auto_gpt_benchmarking test-match --auto-gpt-path /your/path/to/Auto-GPT` | ||
cd Auto-GPT-Benchmarks | ||
python3 auto_gpt_benchmarking test-match --auto-gpt-path /your/path/to/Auto-GPT | ||
|
||
You should only need to use the --auto-gpt-path flag the first time you run it. Afterwards, that will be saved in | ||
|
||
`auto_gpt_benchmarking/completion_fns/auto_gpt_completion_fn.yaml`. | ||
auto_gpt_benchmarking/completion_fns/auto_gpt_completion_fn.yaml. | ||
|
||
To see a full list of available flags you can use run `python3 -m auto_gpt_benchmarking --help` | ||
Some of these are inherited from the openAI evals framework and do not work quite as intended as they are not applicable | ||
|
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