Carlos Mocholí
Carlos Mocholí
I agree that this shouldn't happen. Have you double checked that you called the script as expected and that no other program was running on the GPU? Do you have...
I don't have a solution for you right now. I would need to reproduce the issue. Have you seen this before @rasbt?
Could you do an experiment where you run with both short and long context with precision and precision+quantization for the same model? And report the results
We could follow the pattern used by `to_onnx`: https://github.com/Lightning-AI/lightning/blob/0ca3b5aa1b16667cc2d006c3833f4953b5706e72/src/pytorch_lightning/core/module.py#L1798. Comparing it to the snippet in your linked blogpost, the advantage would be to automatically use `self.example_input_array` (if defined) and call...
Is this still an issue with version 1.7.0? I believe similar bugs have been fixed cc @rohitgr7
Can you provide a reproducible bug snippet? You can update this [script](https://github.com/Lightning-AI/lightning/blob/master/examples/pl_bug_report/bug_report_model.py)
This is a big problem for me because my chart values are very close together (say milliseconds). So the huge difference between 0 and my values results in that the...
cc @kingyiusuen
Hey @Abelarm! You can open a draft PR so we can check your current implementation and discuss it.
The main reason for the revertion of `len` was the impact to existing truthiness checks. That should not be a problem for `str`. @ananthsub do you think the rest of...