Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do we know AUTOMATICALLY if a prompt improved Auto-GPT ? #4190

Closed
1 task done
waynehamadi opened this issue May 14, 2023 · 3 comments
Closed
1 task done

How do we know AUTOMATICALLY if a prompt improved Auto-GPT ? #4190

waynehamadi opened this issue May 14, 2023 · 3 comments

Comments

@waynehamadi
Copy link
Contributor

Duplicates

  • I have searched the existing issues

Summary 💡

Currently someone needs to intentionally modify the code to say " I have beaten challenge A".
But it's possible someone makes an improvement on challenge A but also improves challenge B.

We need to attempt challenges anytime there is a prompt change.

Examples 🌈

No response

Motivation 🔦

No response

@waynehamadi waynehamadi changed the title How do we know if a prompt improved Auto-GPT ? How do we know **AUTOMATICALLY** if a prompt improved Auto-GPT ? May 14, 2023
@waynehamadi waynehamadi changed the title How do we know **AUTOMATICALLY** if a prompt improved Auto-GPT ? How do we know AUTOMATICALLY if a prompt improved Auto-GPT ? May 14, 2023
@waynehamadi waynehamadi self-assigned this May 14, 2023
@Boostrix
Copy link
Contributor

Boostrix commented May 14, 2023

for starters, by keeping track of the costs spent to arrive at a solution ?
In other words, at least steps/API tokens + time ?

In the future, maybe by tracking CPU/RAM utiization as well.

But in general we should gather data for different prompts so that we can use gnuplot to plot performance for each version/commit.

And we should probably start by using GPT to come up with N mutations for a given task (that we know works) and then use those as a baseline for future benchmarking

@github-actions
Copy link
Contributor

github-actions bot commented Sep 6, 2023

This issue has automatically been marked as stale because it has not had any activity in the last 50 days. You can unstale it by commenting or removing the label. Otherwise, this issue will be closed in 10 days.

@github-actions github-actions bot added the Stale label Sep 6, 2023
@github-actions
Copy link
Contributor

This issue was closed automatically because it has been stale for 10 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants