Vision revision and track

[SimoneMartino98]

Hi all @andrewtarzia @matteobecchi;

With this PR i solved:

• Function get_soap doesn't support the selection option. #99
• Fix Video dataclass doc repetition. #89
• Add screenshots/videos to better explain vision GUI. #85
• Fill vision documentation main page. #83

Then I:

• added the dynsight.track module, which now returns Trj.
• Improved the vision GUI by developing an adaptive image rescaling in the visualization (for big images).

I'm ready, whenever you want, for the revision.

[andrewtarzia]

There are some interesting parameters here, which probably need a bit more of an explanation of their ranges and their meaning. I see your doc string, but I think it needs more.

For all these:

• search_range: float = 10,
• memory: int = 1,
• adaptive_step: float = 0.5,
• adaptive_stop: float = 0.95,

[andrewtarzia]

How big can each be? What are appropriate ranges?

[SimoneMartino98]

I took the doc from the original trackpy documentation.
There aren't appropriate ranges for these. They depend on the system size.

[andrewtarzia]

So how does the user select what values to use?

[SimoneMartino98]

trial and error, based on the system they have. (concentration of particles, velocity of them, vibrations).

[andrewtarzia]

Minor things, and changes in the Conversation comments, then all good