Merged
Conversation
we are having some issues with our database queries causing trajectory chunks to be run more than once. I think this is fixed but I need to go through with a fine-tooth comb to make sure committing now since we seem to produce correct trajectories now. previously we had trajectories that would repeat a chunk periodically I think there may still be some non-uniquness sneaking in, but not sure
we have updated the status tracking in the DB to be what I think is mostly correct. the only outstanding issue is the sampling message not getting written until after the labeling message, which is very strange I need to talk to alok about this.
This file contains hidden or 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
1 participant
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.
This represents an attempt to use academy agents + task executors. It works, but relies too heavily on a database to communicate state. We will merge this into main for now, but it will be replaced with a further agentified version where state is more distributed among agents and less centralized in a database.