-
Notifications
You must be signed in to change notification settings - Fork 93
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
Read ForbiddenRelations clauses from json #356
Comments
Replacing
fixed my issue. The bug also seemed to affect the read-in of the Runhistory in SMAC3, when using |
Thanks for the issue and solution! This has been addressed in #346 which we hope to release next week. I'm not sure when SMAC will udpdate to it as they'll likely want to benchmark that nothing is silently broken. That might take another little bit of time |
As mentioned in #352, there still is some work to be done on the documentation side of things for
ForbiddenRelations
. Today I encountered another problem when trying to read in aConfigurationSpace
from a.json
file, created with ConfigSpace.Version: 0.7.1
Error:
Code to reproduce:
Tracing:
It seems like the following constructor:
ConfigSpace/ConfigSpace/read_and_write/json.py
Lines 705 to 721 in ce27ba2
is never called, which should happen at
ConfigSpace/ConfigSpace/read_and_write/json.py
Line 678 in ce27ba2
Instead,
ConfigSpace/ConfigSpace/read_and_write/json.py
Lines 683 to 687 in ce27ba2
is called, which in turn causes the accession attempt of
'name'
, which is not present in theForbiddenRelations
clauseThe text was updated successfully, but these errors were encountered: