Very close trials in Module 3, but not accepted by autograder #25
-
My stuff is only off by about 0.5 ~0.2% and it says in the debug console the test will not be exactly the same. Something said in the output:
The error: AssertionError: Expected first suggested experiment issued to run_color_experiment to be approximately
{'R': 255,
'G': 26,
'B': 210,
'ch410': 219.33087856963076,
'ch440': 248.248387805653,
'ch470': 282.9731413261822,
'ch510': 268.15146335347225,
'ch550': 239.06822906707887,
'ch583': 240.12586524637015,
'ch620': 273.09731873935584,
'ch670': 237.84121011577813}
got
{'R': 254.36590522527695,
'G': 26.613429933786392,
'B': 209.8596078157425,
'ch410': 219.26391480929513,
'ch440': 248.22841161673279,
'ch470': 283.04441855109593,
'ch510': 268.31622424188777,
'ch550': 239.31004096667493,
'ch583': 240.21734078897398,
'ch620': 272.7421011488162,
'ch670': 237.3737462995075} log: |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @kenzo-aspuru-takata, it looks like you might be optimizing over a continuous space. If you specify a float for the bounds (e.g., |
Beta Was this translation helpful? Give feedback.
Hi @kenzo-aspuru-takata, it looks like you might be optimizing over a continuous space. If you specify a float for the bounds (e.g.,
0.0
) Ax interprets this as a continuous parameter, but the RGB values are meant to be integer values. If you specify an integer (e.g.,0
) Ax will interpret this as an integer parameter. The type can also be specified explicitly, but the assignment README doesn't go over that.