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

Create MinerRegistry and Evaluation Pipelines #334

Merged
merged 23 commits into from
Jan 27, 2025

Conversation

mccrindlebrian
Copy link
Contributor

@mccrindlebrian mccrindlebrian commented Jan 25, 2025

  1. Add a generalized MinerRegistry to keep track of generic tasks w/ updates that includes miner credibilities and aggregation functionalities
  2. Add a EvaluationRegistry that holds all the eval pipelines for different tasks
  3. Add RewardBase and reward stacks for different tasks inside of the evaluation registry

@mccrindlebrian mccrindlebrian changed the title Refactor validator Create MinerRegistry and Evaluation Pipelines Jan 26, 2025

required_files_extensions = ["cpt", "log"]

self.pdb_location = pdb_location
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should move towards class designs that don't change states as we use them? ie, not assigning new class variables in functions, all of them should be defined in the init function etc.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

idea with these evaluators is that we would have many instances of them (one for each miner). But if we don't want to do that, then I agree with you

for miner_uid in miner_uids:
self.registry[miner_uid] = {}
for task in self.tasks:
self.registry[miner_uid][task] = {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make this a pydantic class?

Copy link
Contributor

@Sarkosos Sarkosos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mccrindlebrian mccrindlebrian merged commit cd3bd73 into staging Jan 27, 2025
@mccrindlebrian mccrindlebrian mentioned this pull request Jan 27, 2025
@mccrindlebrian mccrindlebrian deleted the refactor-validator branch March 10, 2025 15:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants