You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned on Zulip, we should collate all of the "convenience wrapper" functions (introduced in #282, plus those introduced going forward) into a single example to demonstrate what's on offer.
In theory, this could be combined with #415 , i.e. it could form the same example. The rationale is that it’s useful to visualise trajectories and occupancy heatmaps in the context of quantifying time spent in various regions of interest.
I could work on writing that example next week, alongside #317 . I’m offering for three reasons:
Sometimes having a different person (who didn’t develop the feature) create the examples can be beneficial, as they bring a fresh, “outside” perspective.
It might help free up your limited time to focus on building new features (e.g. the napari widget for drawing shapes).
Happy to hand this over to you if you'd like it. As you say, it'll also be a good check that we're implementing the features in a sensible / intuitive way!
As mentioned on Zulip, we should collate all of the "convenience wrapper" functions (introduced in #282, plus those introduced going forward) into a single example to demonstrate what's on offer.
plot_trajectory
(Plotting wrappers: Head Trajectory #394) might want to come out of the current example it is in if we do this.plot_occupancy
(Plotting Wrappers: Occupancy Histogram #403) will need a new example, but it fits thematically alongsideplot_trajectory
.The text was updated successfully, but these errors were encountered: