Closed zouter closed 5 years ago
Forgot to mention:
infer_trajectory
)I propose the following:
If a wrapper contains a trajectory, use trajectory
Otherwise use dataset
This makes the most sense in the two main dynwrap use cases: creating a trajectory and working with it (i.e. adding a root or calculating a dimensionality reduction), and creating a dataset and working with it (i.e. adding prior information or running a TI method)
This proposal is in branch renamefactorisation
To enhance consistency, I added "common" parameters to the dynwrap object. See https://github.com/dynverse/dynwrap/commit/4438600f67b1c42a7b03bf1468f7e5af94e526b5
Fixed by #125
Right now the first argument of most dynwrap functions can be:
Possible solutions:
Any preference @rcannood ?