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
I have an idea that I believe will be able to unify all functionality currently present in e.g. evolve, visited_obstacles!, escape_time and similar (timeseries is excluded probably due to its interpolating nature). We could have a single function evolve or whatever its called that evolves until a condition is met: this condition could be total amount of time, total amount of collisions, reaching a specific obstacle, whatever. You name it! it can be specified via a single function.
Then, one more other argument would specify what kind of data should be collected. I wonder how easy this really is to do, but my argument would be that you would specify what kind of data to "collect". The huge difficulty here is the "kind of data" vastly differs: from integers (e.g. which obstacles you visited), to floats (how long you evolved for), to tuples of svectors (position and velocity at collision).
But maybe we can provide some "self-made" functions for data collection.
I have an idea that I believe will be able to unify all functionality currently present in e.g.
evolve, visited_obstacles!, escape_time
and similar (timeseries is excluded probably due to its interpolating nature). We could have a single functionevolve
or whatever its called that evolves until a condition is met: this condition could be total amount of time, total amount of collisions, reaching a specific obstacle, whatever. You name it! it can be specified via a single function.Then, one more other argument would specify what kind of data should be collected. I wonder how easy this really is to do, but my argument would be that you would specify what kind of data to "collect". The huge difficulty here is the "kind of data" vastly differs: from integers (e.g. which obstacles you visited), to floats (how long you evolved for), to tuples of svectors (position and velocity at collision).
But maybe we can provide some "self-made" functions for data collection.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: