Skip to content

Commit b6233b1

Browse files
committed
add FAQ docs on dtype
1 parent 20a9be1 commit b6233b1

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

docs/guide/faq_errors.md

+3
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,9 @@
1515
`nequip` cannot and does not check the consistency of units in inputs you provide, and it is your responsibility to ensure consistent treatment of input and output units
1616
```
1717

18+
- **Q**: What floating point precision (`torch.dtype`) is used in the `nequip` framework?
19+
20+
**A**: `float64` precision is used for data (inputs to model and reference labels). Either `float32` or `float64` precision can be used as the `model_dtype` (which is a mandatory hyperparameter of models in the `nequip` framework). If `float32` precision is used for `model_dtype`, the model will cast down from the `float64` inputs (e.g. positions) and cast up the outputs (e.g. energy) to `float64`. A major change in the post-revamp `nequip` framework is that NequIP or Allegro models keep the initial embeddings in `float64` before casting down if `model_dtype=float32` for better numerics.
1821

1922
## Commons Errors
2023

0 commit comments

Comments
 (0)