tensorflow / tensorflow/probability
VariationalGaussianProcess layers can't handle batch size of 1
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 4.4k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
VariationalGaussianProcess layers cause models to raise InvalidArgumentErrors when running with a batch size of 1. This occurs both in model training and inference.
Custom code for replication is not required, the VGP tutorial itself crashes when a batch size of 1 is used.
Error message:
InvalidArgumentError: Requires start <= limit when delta > 0: 0/-1 for 'sequential_1/variational_gaussian_process_1/sequential_1_variational_gaussian_process_1_sequential_1_variational_gaussian_process_1_transposesequential_1_variational_gaussian_process_1_Independentsequential_1_variational_gaussian_process_1_VariationalGaussianProcess/value/sequential_1_variational_gaussian_process_1_sequential_1_variational_gaussian_process_1_transposesequential_1_variational_gaussian_process_1_Independentsequential_1_variational_gaussian_process_1_VariationalGaussianProcess/sample/sequential_1_variational_gaussian_process_1_transpose/forward/range' (op: 'Range') with input shapes: [], [], [] and with computed input tensors: input[0] = <0>, input[1] = <-1>, input[2] = <1>.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the VGP tutorial referenced in the report and run it with a batch size of 1 during both training and inference. Trace the VariationalGaussianProcess layer at the failing Range operation, then verify that the tutorial completes without the reported InvalidArgumentError for batch size 1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- machine-learning
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100