ziatdinovmax
commented
1 year ago @matthewcarbone I think the biggest contributors to the slowdown are the notebooks that assume access to a GPU, such as gpax_viGP.ipynb, GPax_MultiTaskGP_BO.ipynb, and gpax_viDKL_plasmons.ipynb, but it makes sense to adjust num_warmup and num_steps for the smoke test in all of them. I don't think the size of the datasets is a major issue since they all use pretty small/toy datasets.
@ziatdinovmax referencing your suggestion in #50. The way to do this is to add an environment variable that is detected by the notebook. If, for example,
SMOKE_TEST==1, we simply adjust how many iterations things train for, the size of datasets, stuff like this. Again GPyTorch has some good examples of how this can work in practice (they run the tests on their docs but it doesn't matter).