FAQ

What is BayBE’s backwards compatibility policy?

BayBE is in a state of constant development. As part of this, interfaces and objects might change in ways breaking existing code. We aspire to provide backwards support for deprecated code of the last three minor versions. After this time, old code will generally be removed. Both the moment of deprecation and full removal (deprecation expiration) will be noted in the changelog.

Do I need to create a campaign to get recommendations?

No, creating a campaign is not mandatory. BayBE offers two entry points for generating recommendations:

For more details on when to choose one method over the other, see here.

BayBE recommends A but experimentalists do B. What now?

Don’t panic and grab your towel. Recommendations from BayBE are just … well, “recommendations”. The measurements you feed back to BayBE need not to be related to the original recommendation in any way. In fact, requesting recommendations and adding data are two separate actions, and there is no formal requirement to perform these actions in any particular order nor to “respond” to recommendations in any form.

Note, however, that subsequent recommendations may be affected by earlier steps in your campaign, depending on your settings for the allow_recommending_already_measured and allow_recommending_already_recommended flags.