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
One result which should come out of this issue is that access to individuals should be streamlined. There are several ways to access results from individuals, traj.individual., traj.individuals[i]. etc. Either there should be one possibility to access the results or it should at least be better documented.
So here is the UML of the Trajectory... Now I need to make a link to where in the code are the different parts used. There are four structures for the results which should be concentrated into one, there are two layers on the parameters which should probably be again flattened into one and three elements for the individuals which need to be collected into probably two, the ID of the current individual and then a data structure to hold the individuals themselves.
The functions should also be revisited, they mimic the old Trajectory in pypet but probably things can be highly simplified.
here are two layers on the parameters which should probably be again flattened into one and three elements for the individuals which need to be collected into probably two, the ID of the current individual and then a data structure to hold the individuals themselves.
Sounds good. That would make things easier if the trajectory is flattened
Create a view on the trajcetory for cleaning up purposes.
The text was updated successfully, but these errors were encountered: