Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A* to a location and a given set of observations #194

Open
Zannick opened this issue Jul 15, 2024 · 0 comments
Open

A* to a location and a given set of observations #194

Zannick opened this issue Jul 15, 2024 · 0 comments

Comments

@Zannick
Copy link
Owner

Zannick commented Jul 15, 2024

We had a best route with this segment:

494. Move to Annuna > Mirror Match > West Gap
495. ! Do Recall Drone
496. Move... to Uhrum > Annuna Corridor > Block East
497. Move... to Uhrum > Annuna Corridor > Block West ==
498. FastTravelKiengirwarp to Menu > Kiengir Map > Uhrum East

The item before this segment is collected as drone, and the item after this segment is collected as Indra; we need Indra later to take a specific Throw Drone edge. However, we can't improve this segment with our current A* helpers, because they go straight to the next item, which is certainly possible to get as drone, but then we can't perform that Throw Drone without spending even more time correcting our course. (I believe this segment was found before we added the Fast Travel point at Indra's location here, and then was never improved because we never processed another route that would match.

If we have the observation set from the subsequent item state, we could instead perform our A* search for a state that matches that observation, and thus not take any state that can't complete the rest of the route as-is.

One complication is that A* would work better if we can estimate how long it would take to change a differing observation to one that matches... But likely we should just use A* on the canon location and have a strict upper bound on time that's the original.

Zannick added a commit that referenced this issue Jul 16, 2024
Zannick added a commit that referenced this issue Jul 16, 2024
Contains workarounds for #195: generated code does not clear observations, and analyzer now re-observes access after observing everything else.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant