Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Short Trajectories #64

Open
ryanredward opened this issue Jul 28, 2017 · 5 comments
Open

Short Trajectories #64

ryanredward opened this issue Jul 28, 2017 · 5 comments

Comments

@ryanredward
Copy link

Is there any way to manually label trajectories that are too short to be segmented? Currently, I have not been able to label any direct findings because of this issue.

Please advise. Thanks!

@avouros
Copy link
Collaborator

avouros commented Jul 28, 2017

Hi,

All of the unsegmented trajectories are automatically assigned to Direct Finding. You can change this by manually labelling them during the results generation step

DF and AT is used (usually) only on the full trajectories (this is why they have 'trajectory' as a note). To label full trajectories load my_trajectories.mat inside the settings subfolder of your project folder.

The above applies on version 4 of the software which will be officially out during weekend (still working on some bugs). It will be announced here.

@avouros
Copy link
Collaborator

avouros commented Jul 30, 2017

Hi ryanredward new release (v4.0.2) is out! Check it out and please let us know if you come across any issues.

@avouros avouros added the fixed! label Jul 30, 2017
@lolaBerkowitz
Copy link

Is there anyway to create a training set based on full trajectories(that are shorter than the segment length)? Not all paths shorter than the specified segment length are direct trajectories or approaching target. This is particularly troublesome with my data set.

Looking forward to your response! Thanks!

@avouros
Copy link
Collaborator

avouros commented Sep 4, 2017

Unfortunately no, full trajectories should all be labelled manually. I have put this limitation because our methodology has been tested only on segmented trajectories. Some limited tested on full trajectory classification has been performed but it yields poor classification results due to the fact that full trajectories usually fall under many categories.

However, you can label unsegmented trajectories during the generation of your results (see https://github.com/RodentDataAnalytics/mwm-ml-gen/wiki/Results#EXTRAS). Then these trajectories will be considered as segments and be analysed along with the rest of your trajectory segments.
(Currently this option is not very user friendly because each time you have to relabel these trajectories, I will try to fix that in the future.)

@lolaBerkowitz
Copy link

Got it thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants