FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Automatically setting agg.path.chunksize? · Issue #4404 · matplotlib/matplotlib · GitHub

Repository navigation

Automatically setting agg.path.chunksize? #4404

Closed as not planned
Closed as not planned

Description

I just realized that agg backends can throw an OverflowError when dealing with large datasets (in draw_path, self._renderer.draw_path throws OverflowError). I wonder if it would be a good idea to automatically set nmax (i.e., the agg.path.chunksize config param) to a larger value and retry the plot.

Activity

  1. added this to the milestone on May 5, 2015
  2. tacaswell commented on May 5, 2015

    Member

    I am not a huge fan of adaptive magic like that.

    @efiring It looks like you added this feature in 2008, thoughts?

  3. efiring commented on May 5, 2015

    Member

    The chunking is disabled by the default value (0) of agg.path.chunksize. There are other conditions on the chunking; it works only for simple lines. I suspect it hasn't been used in many years. Path simplification handles most of the cases where it would have been needed. It's not clear to me that there is any point in keeping it.

  4. tacaswell commented on May 24, 2015

    Member

    @anntzer Do you have an example where this has actually been a problem?

  5. added a commit that references this issue on May 24, 2015
    aa34490
  6. self-assigned this
    on May 24, 2015
  7. anntzer commented on May 24, 2015

    ContributorAuthor

    Basically the same as the ones mentioned by @efiring in #4464, i.e. plotting very long lines.

  8. modified the milestones: , needs sorting on Oct 6, 2022
  9. github-actions commented on Oct 9, 2023

    This issue has been marked "inactive" because it has been 365 days since the last comment. If this issue is still present in recent Matplotlib releases, or the feature request is still wanted, please leave a comment and this label will be removed. If there are no updates in another 30 days, this issue will be automatically closed, but you are free to re-open or create a new issue if needed. We value issue reports, and this procedure is meant to help us resurface and prioritize issues that have not been addressed yet, not make them disappear. Thanks for your help!

  10. added
    status: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.
    on Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

New featurestatus: closed as inactiveIssues closed by the "Stale" Github Action. Please comment on any you think should still be open.status: inactiveMarked by the “Stale” Github Action

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


    Back | FazBrowse Home | New Git URL