ManimCommunity / ManimCommunity/manim
LinearTransformationSceneExample does not work in Colab
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
I'm trying to change the base configurations for LinearTransformationScene, but I get an error. This was not the case when I was using the previous version of Manim a few days ago
## Expected behavior
I was hoping to change the configs without getting an error
## How to reproduce the issue
Following is some example code taken from the docs. The first line was to get it to run in Google Colab (as described in the tutorials section)
```py
%%manim LinearTransformationSceneExample
class LinearTransformationSceneExample(LinearTransformationScene):
def __init__(self):
LinearTransformationScene.__init__(
self,
show_coordinates=True,
leave_ghost_vectors=True,
)
def construct(self):
matrix = [[1, 1], [0, 1]]
self.apply_matrix(matrix)
self.wait()
```
## Logs
Terminal output
```
TypeError: __init__() got an unexpected keyword argument 'renderer'
```
## System specifications
System Details
Google Colab's settings
Python version
```
python3
```
FFMPEG
Output of `ffmpeg -version`:
```
ffmpeg version 3.4.8-0ubuntu0.2
```
## 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 by running the documented LinearTransformationSceneExample in Google Colab with the shown %%manim cell and base configuration arguments. Trace the constructor path associated with the unexpected renderer keyword argument. Done means the example runs in Colab without the TypeError while retaining the requested configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cloud, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100