[WIP] Shadereval tasks #173
Draft
+286
−1
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.
revival of #97
This PR adds the Shadereval tasks, Shadereval looks at "creative coding" by comparing models on shadercode(glsl with Shadertoy.com syntax). There is (currently) two tasks:
shadereval-1: ReturnCompletion as seen in demo space. Using a subset of Shadertoys-fine dataset to predict the return statement of functions. Metric used is
exact_match. The original implementation is hosted as anEvaluationSuiteinside the demo space.shadereval-2: FunctionCompletion as seen in demo space, Using a processed version of the Shadertoys dataset, taking docstrings immediately before a function as a prompt and combines that with the function header as input. Evaluated with a custom metric (hosted in the demo space) that first compares the text statically, and then renders frames of prediction and reference.
The paper for the first task and dataset has been written but not not be published - it can be omitted from this PR since it was more of a prototype.
The second task is nearly done as part of my Thesis, we hope to publish this eventually too. The implementation should be done by October. The dataset is essentially locked but will be renamed. This PR is our reference implementation.
Remaining tasks:
#TODO:...