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
animovement is growing is scope, and that's great!
However, I'm increasingly beginning to think that I'll need to have multiple packages all gathered in a single meta-package to make it easier to maintain. I'm not decided on any of this; e.g. whether the meta package should be called aniverse or animovement, and accordingly whether the reader functions should then be in animovement or anireadr... I think I'm leaning more towards aniverse, and keeping animovement as the reader/format/metadata handling package.
Let's begin to sketch out an idea.
aniverse
animovement
Primarily for all the reader/writer/metadata functions
anisignal
New home for all the signal processing functions, filters
anibehavr
Maybe the classification functions should go in here?
aniphys
Reading relevant physiological data (e.g. incorporating the current respirometr package)
aniplot
Could be an idea to place all the plotting functions in a package and make it optional (or even just have all the check/plot functions in such a package?)
The text was updated successfully, but these errors were encountered:
animovement
is growing is scope, and that's great!However, I'm increasingly beginning to think that I'll need to have multiple packages all gathered in a single meta-package to make it easier to maintain. I'm not decided on any of this; e.g. whether the meta package should be called
aniverse
oranimovement
, and accordingly whether the reader functions should then be inanimovement
oranireadr
... I think I'm leaning more towardsaniverse
, and keepinganimovement
as the reader/format/metadata handling package.Let's begin to sketch out an idea.
aniverse
animovement
anisignal
anibehavr
aniphys
respirometr
package)aniplot
The text was updated successfully, but these errors were encountered: