Skip to content

handling of grid/bin #31

@sheim

Description

@sheim

This is an old todo...

After a state transition, we place the resulting state s_next in a bin. To compute Q_V, we check that the grid-points enclosing that bin are all viable, otherwise we cannot guarantee viability.

This poses a problem when the state s_next lands on a grid-point or a grid-line, since we are the still checking neighboring grid-points, which could be unviable. This particularly happens when we have grid-world things or grid-lines that pass through equilibrium points. For now I've handled grid-world issues by keeping track of things that land direclty on grid-points, but not yet grid-lines...

This is a bit tricky, since to check we would have to keep track of the actual dimensions. The nice thing of Q_map keeping track of the index only is that each entry in Q_map is an integer, instead of a vector (this saves on memory for higher-dimensions). To think about...

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions