Problem:

The Blender folder is quite messy, having all Python code along other files such as the Blender project file, the arrow 3D object file and a paramagnetism image.

Suggestions:

• Python files should be placed inside a src folder, probably config.json should be there too.
• The output folder currently holds rendered videos that are excluded from the GitHub repository. This should be placed somewhere else, probably at the root of the local repository, as it's not relevant to the code.
• The out folder should be named matrices.
• An assets folder would be ideal for files such as arrow.mtl and arrow.obj.
• Many .blend files aren't in use and should be deleted. The only file that's currently in use is spins1D.blend, a better name would be useful (demo.blend?)
• The root folder is quite messy too, and an images folder could be useful. Blender/paramagnetism.png would be better located there.

Whenever ArrowAnimation(axis="z") is used, spins are expected to appear orthogonal to the lattice that's formed when the dimensions are [x,y,1], with x and y above 1.
This is not happening right now, every axis used appears parallel to the lattice, and should be fixed.

We should be using Docsify to document the project.

Must find a way to receive Lucas' automaton output and use it to build a spin matrix.

Code inspiration: https://www.youtube.com/watch?v=YiE9tcoCfhE

We're trying to use the Godot engine in order to be able to show our spin matrices on a web browser, since GDScript follows Python's syntax and godot-python exists. Godot allows exporting a project as HTML5 and also uses WebGL, we must prove this is viable for our intended use.

• Create a simple 2D/3D parameterized spin matrix.
• Export as a website.
• Use GitHub Pages to host the result.

It is expected to be able to move the object position.

• Create a new Blender project
• Code 3D movement
  • Spins should move through the beam's 3D space
    We may use Qiskit to define a spin's destination, measuring a quantum circuit with a Hadamard gate
• Rotation could be random until the final destination is set
  We could use our current paramagnetism operator, being called every X frames

Ideally, the oven, slit, magnets and screen should be programatically created.

• Should be able to set up the length of a spin staying at a certain orientation (keyframe and delta parameters).
• Ideally, it should let users configure the keyframe values matrix by matrix.

Consider this as matrix-to-spin-array metadata.