yt_analysis is sharing code with you

Bitbucket is a code hosting site. Unlimited public and private repositories. Free for small teams.

Don't show this again

yt_analysis / yt http://yt-project.org/

yt is a python package for analyzing and visualizing astrophysical simulation output from a couple simulation platforms. Check out the homepage (there's a link just above!) where we have documentation, a cookbook, and some user community information.

Clone this repository (size: 41.0 MB): HTTPS / SSH 
hg clone https://bitbucket.org/yt_analysis/yt
hg clone ssh://hg@bitbucket.org/yt_analysis/yt

Issues

#239 Grid partitioning should only store bounding-box information

Reported by yt_analysis (last edited )

Imported Ticket

  • Summary: Grid partitioning should only store bounding-box information
  • Component: extensions
  • Milestone: 2.1
  • Reporter: mturk
  • Owner: mturk
  • Resolution: wontfix
  • Status: closed
  • Created: 1266971811000000
  • Description: If we only store the slice information -- i.e., min/max indices along all three axes -- then we save on the memory utilized during a volume rendering. We can and should store the original pointers to the grid data, but we do not necessarily need to store the subsections.

Update to Ticket

  • Author: mturk
  • Changetime: 1266971823000000
  • Field: status
  • Oldvalue: new
  • Newvalue: assigned

Update to Ticket

  • Author: mturk
  • Changetime: 1266971823000000
  • Field: owner
  • Oldvalue: britton
  • Newvalue: mturk

Update to Ticket

  • Author: mturk
  • Changetime: 1266971823000000
  • Field: milestone
  • Oldvalue:
  • Newvalue: 2.0

Update to Ticket

  • Author: mturk
  • Changetime: 1266971823000000
  • Field: comment
  • Oldvalue: 1
  • Newvalue:

Update to Ticket

  • Author: mturk
  • Changetime: 1282268099000000
  • Field: milestone
  • Oldvalue: 2.0
  • Newvalue: 2.1

Update to Ticket

  • Author: mturk
  • Changetime: 1282268099000000
  • Field: comment
  • Oldvalue: 2
  • Newvalue: The grid partitioning has improved substantially in terms of being able to store and load multiple types of bricks. However, this bug is still valid. In the current state of the grid partitioner, the slice information *is* returned, but this is then not used. For the purposes of a single-pass at homogenization, it could be, but it has yet to be.

Update to Ticket

  • Author: mturk
  • Changetime: 1296268343501842
  • Field: status
  • Oldvalue: assigned
  • Newvalue: closed

Update to Ticket

  • Author: mturk
  • Changetime: 1296268343501842
  • Field: resolution
  • Oldvalue:
  • Newvalue: wontfix

Update to Ticket

  • Author: mturk
  • Changetime: 1296268343501842
  • Field: comment
  • Oldvalue: 3
  • Newvalue: I believe that before we do this, we should investigate more fully faster mechanisms for generating the vertex-centered data.
Status: wontfix Responsible: nobody Type: enhancement Priority: major
Milestone: 2.1 Component: analysis_modules Version: none

Attachments

No attachments added for this issue yet.

Comments and changes

No comments added for this issue yet.

Add comment / attachment

Show/hide preview

Verification: Please write the text from the image in the box (letters only)

captcha

Is that you, Humanoid? Is this me?