-
Notifications
You must be signed in to change notification settings - Fork 3
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
Helenlei/ai gpt costing #435
Conversation
[diff-counting] Significant lines: 151. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, Helen! Code is streamlined and I like that we have different options to only look at courses with a minimum number of reviews - it'll be a huge help as we look into OpenAI costing. The one thing I can point out is in the '/costing' route it would be helpful to get the minimum from the request body and pass it in to the function. Great work overall :)
Great work Helen! The structure of the code is very easy to follow. I think something that might also help with the OpenAI costing would be to look at the average number of distinct words in each review. |
|
This is amazing Helen - great to see you getting the pieces connected together and running the functions on our staging database. Here are some more reference points which you can use to provide & calculate more concrete prices from https://openai.com/pricing (4 characters = 1 token) and GPT-4 and GPT-3.5 turbo have some pretty drastic price points. Currently discussing production-level database access with Sarah right now - looking like we may be able to get temporary read access first. |
…ting' into helenlei/ai-gpt-costing
Script that can be used to get the numbers needed to calculated the total costs for creating "cornellian says" summaries, depending on which model we use. For example, below are the results for if we wanted to create summaries for all courses that have at least 3 reviews.
