Fix Version/s: None
When using afw.display with the Firefly backend, writing ellipses with buffering does not draw ellipses:
for record in src256[::10]:
display.dot(record.getShape(), record.getX(), record.getY())
It works without the buffering.
- is triggering
DM-15245 bug fix in regions API: draw the correct regions, discard the wrong ones
Questions for Robert Lupton: Should afw.display.dot check for NaNs in the ellipse shape parameters and refrain from sending them?
When a backend receives an ellipse with NaN shape parameters, is it sufficient to silently ignore these? Or should some sort of error be communicated back to the user?
I think you can silently ignore NaNs – they aren't the display code's problem.
It is a bug in Firefly. Firefly intends to ignore nani silently and render other correct ones based on current development.
The bug in Firefly has been fixed in
No action is needed on the Python side. Ellipses with NaN shapes are silently discarded by the backend.
The story points are for analyzing the problem and testing.
NaN values in the catalog cause the problems. When not buffering, the regions are sent individually and the valid ellipses are drawn. When buffering is on, the regions are sent all at once and the NaN-shape ones cause all the regions to fail.