abyrd
commented
8 months ago The UnsupportedOperationException is indirectly caused by hitting the testing code path introduced in 9a1d114, which causes a Grid destination PointSet included in the single point request to be taken as the destinations for travel time, while subsequent code generating and recording travel times calls methods only defined on WebMercatorGridPointSet or FreeFormPointSet.
The log warnings and assertions introduced in 9a1d114 and 3b3d4ff of PR #896 caught the fact that destination PointSet objects are not always set on the destinations field of single point requests before processing (i.e. TravelTimeSurfaceTask.destinationPointSets may be null or empty). I was thrown off by the local variable destinations around TravelTimeComputer L90 which is always initialized locally (with a WebMercatorPointSet in the simple case) but that value is not reflected on the destinationPointSets field of the TravelTimeSurfaceTask object itself. In fact, single point requests only have destinationPointSets set when we're calculating accessibility. The PointSets are then expected to be ones that have defined densities, like Grid or FreeFormPointSet, not the density-less WebMercatorGridPointSet. But that local variable still gets set to a WebMercatorGridPointSet.
The fact that we can hit this code path in normal usage, and the fact that the local destinations variable is set to a different PointSet than the one on the request, implies it's possible to cause problems analogous to the one observed in the Simpson Desert tests (which led me to create this code path and assertions): a mismatch between the number of actual destination points and the number of destinations for which travel times are computed, which can fail silently if the latter is smaller than the former. The intended interface and behavior needs to be clarified, and assumptions about aligned grids need to be validated with assertions.
A check to this effect is already in place at TravelTimeReducer#checkOpportunityExtents. I will investigate why this was not being hit in the Simpson Desert tests, and whether it's being hit in single-point requests calculating accessibility (like those with decay functions).
Using UI and project at https://analysis-a2ezz7l8s-conveyal.vercel.app/regions/63a95f7328b9ff8f79b276ee/analysis?projectId=63a968e7e94bbb2013007634&_shouldResolveHref=true&scenarioId=baseline
Using destinations
z9 gaussian west gridded fracand logistic decay function with SD=2.Using backend and worker from
2023-fall-releasecluster branch (v6.9-10-gfbd1062).Exception is as follows:
The
UnsupportedOperationExceptionis from the base class (non-)implementation ofPointSet#getPointsInEnvelope. The subclasses WebMercatorGridPointSet and FreeFormPointSet implement it, but Grid and GridTransformWrapper do not. This code path is calling an unimplemented method on a Grid. This must have worked previously because we could calculate accessibility results with decay functions during single point requests.