You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the get_candidates function of the zerocost branch optimizers Bananas and Npenas there is a discrepancy between how candidates in the next_batch are stored.
If the acquisition function is being optimized via "random_sampling", then model is being stored:
...
candidates.append(model)
Otherwise, if it is being optimized via "mutation", then model.arch is being stored:
...
candidate=archcandidates.append(candidate)
However, the function get_best_candidates (which is called directly after get_new_candidates) treats candidates as a list of models:
Does this imply that the optimization of the acquisition function via "mutation" is not used in the main loop of either Bananas or Npenas? If so, how and when should this option be used?
The text was updated successfully, but these errors were encountered:
In the
get_candidates
function of thezerocost
branch optimizersBananas
andNpenas
there is a discrepancy between how candidates in thenext_batch
are stored.If the acquisition function is being optimized via
"random_sampling"
, thenmodel
is being stored:Otherwise, if it is being optimized via
"mutation"
, thenmodel.arch
is being stored:However, the function
get_best_candidates
(which is called directly afterget_new_candidates
) treatscandidates
as a list of models:Does this imply that the optimization of the acquisition function via
"mutation"
is not used in the main loop of eitherBananas
orNpenas
? If so, how and when should this option be used?The text was updated successfully, but these errors were encountered: