This is an old revision of the document!
Table of Contents
Computer
Terminology
Internet
Shaders
Machine Learning
anaconda setup and github repo cloning
Image-tagging
Gaussian Splatting workflow
| Name | Description |
|---|---|
| Supervision | Computer vision tools |
| Depth map generator | Depth map generator |
| Neural crossbreed | Blend inbetween faces |
| Eulerian Motion Fields | Animating Pictures with Eulerian Motion Fields |
| Facefusion | Replace face in video from single images |
| DiffMorpher | Blend inbetween images |
| TagGUI | Adding and editing image tags and captions |
| Rerun | Visualization toolkit for multimodal data |
| ComfyUI | Node based stable diffusion tool |
| Claude | AI assistant, very good for coding |
| Tracking Everything Everywhere All at Once | AI point Tracker |
Slashes
Forward slashes (/) are the standard in Git and most cross-platform development tools
Backslashes (\) are traditional in Windows path notation
For best compatibility, I recommend choosing forward slashes. Here's why:
Git internally uses forward slashes regardless of the platform
Forward slashes work consistently across operating systems
Most Git documentation and examples use forward slashes
It reduces potential escape character issues in command-line operations
Choosing forward slashes will ensure better compatibility if you ever need to work with your repository on different operating systems or if you collaborate with others using non-Windows systems.
Either option will work for basic functionality, but forward slashes are generally considered the better practice in Git environments, even on Windows.
