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

1174 replace hard coded indices in runhistory #1180

Open
wants to merge 5 commits into
base: development
Choose a base branch
from

Conversation

LukasFehring
Copy link
Collaborator

No description provided.

]

config_ids_to_serialize = set([entry[0] for entry in data])
data[k.config_id] = {
Copy link
Collaborator

Choose a reason for hiding this comment

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

this might need to be adapted

self.add(
config=self._ids_config[int(entry[0])],
config=self._ids_config[int(key)],
Copy link
Collaborator

Choose a reason for hiding this comment

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

this might need to be adapted

1733133181.21695, # end_time
{} # additional_info
],
"data": {
Copy link
Collaborator

Choose a reason for hiding this comment

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

AFAIK the config id is a unique configuration without the budget and the instance. If this is the case, we need a different data structure, because currently we would overwrite evaluated trials with the same configs but different budgets/instances. I would propose a list of dictionaries.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I will check that and get back to you

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I will adapt this accordingly

@benjamc
Copy link
Collaborator

benjamc commented Dec 14, 2024

also please update CHANGELOG.md accordingly by briefly describing the change and the implications and mention the PR number.

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