Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: display_firefly
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:SUIT Sprint 2018-08
-
Team:Science User Interface
Description
DM-15213 is fixing the bug in Python calling function for LSST. We need also to fix it in the JS API.
I checked region file upload in current dev version. The non-parsable regions are ignore already in UI. API should behave the same.
Attachments
Issue Links
- is triggered by
-
- Done
- links to
Activity
| Assignee | David Shupe [ shupe ] | Cindy Wang [ cwang ] |
| Summary | CLONE - display.dot of ellipses fails with display_firefly when buffering | bug fix in regions API: draw the correct regions, discard the wrong ones |
| Description |
When using {{afw.display}} with the Firefly backend, writing ellipses with buffering does not draw ellipses:
{code:python} with display.Buffering(): for record in src256[::10]: display.dot(record.getShape(), record.getX(), record.getY()) {code} It works without the buffering. |
I checked region file upload in current dev version. The non-parsable regions are ignore already in UI. This need to be done in the API too. It works without the buffering. |
| Description |
I checked region file upload in current dev version. The non-parsable regions are ignore already in UI. This need to be done in the API too. It works without the buffering. |
I checked region file upload in current dev version. The non-parsable regions are ignore already in UI. API should behave the same. |
| Epic Link |
|
| Sprint | SUIT Sprint 2018-09 [ 739 ] |
| Sprint | SUIT Sprint 2018-09 [ 739 ] | SUIT Sprint 2018-08 [ 738 ] |
| Status | To Do [ 10001 ] | In Progress [ 3 ] |
| Reviewers | David Shupe, Tatiana Goldina [ shupe, tatianag ] | |
| Status | In Progress [ 3 ] | In Review [ 10004 ] |
| Remote Link | This issue links to "pull request (Web Link)" [ 17801 ] |
| Status | In Review [ 10004 ] | Reviewed [ 10101 ] |
| Resolution | Done [ 10000 ] | |
| Status | Reviewed [ 10101 ] | Done [ 10002 ] |
API uses the region parser done by JS code. It intends to skip the region with wrong description silently and render other regions with good description. It is a bug in the region parser of JS code causing the issue.