ManimCommunity / ManimCommunity/manim
[LinearTransformationScene] the unit vector j doesn't move with the same acceleration as the y-axis
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40.9k
- Forks
- 3.1k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 25
Description
## Description of bug / unexpected behavior
The unit vector j and the y-axis have different speeds. See video below.
## Expected behavior
They are always in the same line during transformation.
## How to reproduce the issue
Code for reproducing the problem
```py
class Test1(LinearTransformationScene):
def __init__(self):
LinearTransformationScene.__init__(self, include_background_plane=False)
def construct(self):
matrix = [[1, 3], [-2, 0]]
self.apply_matrix(matrix)
self.wait()
```
## Additional media files
Images/GIFs
https://user-images.githubusercontent.com/7588612/124348525-fdc9fc00-dc1c-11eb-873e-055a2a2ccdb2.mp4
## Logs
Terminal output
```
PASTE HERE OR PROVIDE LINK TO https://pastebin.com/ OR SIMILAR
```
## System specifications
Doesn't seem to be relevant.
System Details
- OS (with version, e.g Windows 10 v2004 or macOS 10.15 (Catalina)):
- RAM:
- Python version (`python/py/python3 --version`):
- Installed modules (provide output from `pip list`):
```
PASTE HERE
```
LaTeX details
+ LaTeX distribution (e.g. TeX Live 2020):
+ Installed LaTeX packages:
FFMPEG
Output of `ffmpeg -version`:
```
PASTE HERE
```
## Additional comments
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 LinearTransformationScene and its apply_matrix entry point, using the reproducer in the issue to observe the unit vector j and y-axis during the transformation. Trace how both objects are animated and verify the result with the provided matrix: they should remain on the same line throughout the transformation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 38/100