consider giving "mover not near the center" its own h2 section

[MrtnKk]

I've seen talks (like BYW meeting 2023/09/07) about users discussing movers not near the center/at the edges of subjects while the classification question clearly states "Is there a mover that passes near the center of this frame?"

This use case is already addressed in the current FAQs under the h2 section "How to Use the Site" where it is a) kind of buried in there and b) is only based on the assumption, it's due to the machine learning algorithm not working properly.

Turns out, users deliberately discuss movers not near the center even though the classification question asks otherwise.

Therefore I suggest giving this topic its own h2 section so it's easier to find and address. Also mentioning it's not always the machine learning algorithm at fault but sometimes just a coincidence/a comoving object/…

[MrtnKk]

Consider adding some guidelines on how to address a mover's location when not near the center. Like let the user explicitly specify where within the flipbook the mover can be seen so that moderators/researchers can quickly see what object we're talking about.

See my discussion with SAlexandrov at Subject 91181480 where I suggested a shortcode by making use of the grid in the Cool neighbors flipbooks and combined it with the BYW:P9 Tygo form 'location' division.

r = row, c = column (Cool Neighbors)
t = top, m = middle, b = bottom (BYW:P9 Tygo horizontal division)
l = left, c = center, r = right (BYW:P9 Tygo vertical division)

A moving object in the upper right corner of the square in the first row and third column would then be:
'13tr' → row 1, column 3, top right

It's just a rough idea and may be too complicated but since the flipbooks don't show any R.A or dec. values, it's time-consuming to always have to open up WiseView and figure out the location of the object by the given R.A./dec. values.

[MrtnKk]

Subject 91131270 is a good example for the need of clear communication of 'off-center' movers.