[scheduler] fix some scheduler dtype error #2992
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
when use nvidia gpu, the dtype of timesteps is float64 and the dtype of timesteps_interpol is float32, but they will be pushed into same torch.stack. This bug will make some optimization failed. For example, when I use oneflow to mock torch, torch.stack will push timesteps_interpol and timesteps which has different dtype, and then oneflow will clash.