search

beelabhmc / ant_tracker

Track ant movement in a lab setting using ML
http://hmcbee.blogspot.com/
1 stars 1 forks source link

Specify Important Edges #29

Open JarredAllen opened 5 years ago

JarredAllen commented 5 years ago

For ROIs, we need some way to specify which edges are relevant and could have ants crossing them.

The current plan is to go into roimodify.py and add a tool for selecting the important edges for each ROI. Then, in the edgefromtrack.py script, we need to modify the file to only allow ants to enter and exit from one such edge, if there's one.

JarredAllen commented 5 years ago

Specifying the important edges has been handled as of ea3a27d5d, but no automatic detection is in place.

The code still doesn't do anything with the values, either.

mdonaldsonmatasci commented 5 years ago

Not quite sure what you meant by automatic detection, but I realized you could by default assume that in a rectangle the short edges are the important ones, and in any other shape assume all edges are important? This would probably get it right most of the time.

JarredAllen commented 5 years ago

@mdonaldsonmatasci That's what I meant by automatic detection.

mdonaldsonmatasci commented 5 years ago

ok sounds good

JarredAllen commented 5 years ago

As of 9b4827f, the code now uses the important edges and classifies tracks as going from one important edge to another important edge only, if a user specifies them. Because specifying the important edges is easy to do, I'm going to call enabling the code to automatically guess at which edges are important to be a low-priority concern.

mdonaldsonmatasci commented 5 years ago

It may be easy, but if we have to do it manually 70 8 3 times (for each video) it's pretty laborious. Would it be possible to specify them once for a whole set of videos, like all of Pi 8 from experiment 1? That would be only 24 times which seems more doable.

On Tue, Jul 23, 2019, 10:01 Jarred Allen notifications@github.com wrote:

As of 9b4827f https://github.com/beelabhmc/ant_tracker/commit/9b4827fdcece46ddc3cd4e0f0873316246772459, the code now uses the important edges and classifies tracks as going from one important edge to another important edge only, if a user specifies them. Because specifying the important edges is easy to do, I'm going to call enabling the code to automatically guess at which edges are important to be a low-priority concern.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/beelabhmc/ant_tracker/issues/29?email_source=notifications&email_token=ACEBOCHFNEDZM277XKQIZCTQA42PVA5CNFSM4IFI24YKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2TY37I#issuecomment-514297341, or mute the thread https://github.com/notifications/unsubscribe-auth/ACEBOCG2FFSCDWEBYJFOC2TQA42PVANCNFSM4IFI24YA .

JarredAllen commented 5 years ago

@mdonaldsonmatasci I'll look into reusing manually specified ROIs in a bit, but my gut feeling is that it should be possible.