Imported Ticket
- Summary: Hierarchy attributes should be kept in a recarray
- Component: lagos
- Milestone: 2.0
- Reporter: mturk
- Owner: mturk
- Resolution: wontfix
- Status: closed
- Created: 1186084734000000
- Description:
Update to Ticket
- Author: mturk
- Changetime: 1186413562000000
- Field: status
- Oldvalue: new
- Newvalue: assigned
Update to Ticket
Update to Ticket
- Author: mturk
- Changetime: 1188334826000000
- Field: milestone
- Oldvalue: First Public Release (0.2)
- Newvalue: Version 0.3
Update to Ticket
Update to Ticket
- Author: mturk
- Changetime: 1197341506000000
- Field: milestone
- Oldvalue: Version 0.3
- Newvalue: Version 0.4
Update to Ticket
- Author: mturk
- Changetime: 1197341506000000
- Field: comment
- Oldvalue: 3
- Newvalue: This fits well with Ticket
#45, because it will be more useful for generalized AMR reading.
The reasons for doing this are two-fold --
1. Using a recarray means we use pointers in the individual grid files.
2. Using a recarray de-pollutes the namespace of the Hierarchy object.
Update to Ticket
- Author: mturk
- Changetime: 1207601128000000
- Field: status
- Oldvalue: assigned
- Newvalue: closed
Update to Ticket
- Author: mturk
- Changetime: 1207601128000000
- Field: resolution
- Oldvalue:
- Newvalue: wontfix
Update to Ticket
- Author: mturk
- Changetime: 1207601128000000
- Field: comment
- Oldvalue: 4
- Newvalue: No, I have changed my mind. recarray does not work for us because it is slightly less flexible. The hierarchy, even in extremely large datasets, is a large chunk of memory. But this is not the way to fix that.