A Hyperopt search space uses hp.choice to select among model options. After fmin finishes, the returned value for that choice is not the readable option the engineer expected. What explains this behavior?
Answer & explanation
Correct answer: C
WHY C: Hyperopt's fmin returns the index of the selected hp.choice option, and space_eval can map that back to the actual configured value.
WHY NOT A: The returned value is the choice index, not a loss, and no join is involved.
WHY NOT B: The behavior is intentional, not a JSON serialization loss.
WHY NOT D: hp.choice supports categorical branches directly; nothing is rounded.
WHY NOT E: The choice value is recoverable with space_eval without relying on Trials attachments.