[SEER] Seer plumbing and Testing #841
Draft
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Setup new routes just for seer.
/api/seerRewired the seer frontend to use this route.
Created a REPO for seer testing. https://github.com/SAGE-3/seer
Mahdi will probably replace this with his own repo but just for testing right now.
Has ACTIONS to build new images when updated.
Right now it just takes what ever you put in the prompt, sends it to the nodejs proxy, which passes it to the SEER python docker container, which takes the prompt and adds it to
print(\"$prompt\")and sends it back to the frontend.All just preliminary testing.
Screen.Recording.2024-01-30.at.3.50.10.PM.mov