OH. I see. You are providing a multi-level pointer structure to the data
(almost like a relational database "cursor"), and not _replacing_ the
original data stucture hierarchy. If so, then your structure is pretty
efficient, since its components will not be allocated, simply associated. Is
that it?
Alvaro Fernandez
|-----Original Message-----
|From: Fortran 90 List [mailto:[log in to unmask]]On Behalf
|Of Jing Guo
|Sent: Monday, July 01, 2002 10:52 AM
|To: [log in to unmask]
|Subject: Re: Help needed with array sectioning
|
|
|Alvaro Fernandez wrote:
|>
|> Hmmm. I'm a little lost... I understand the idea, but the
|"storage" field is
|> only real values. You can point at any slice of it with the weeklyrecords
|> pointer, true, but you are only able to reference real values, right? Yet
|> for instance Hourly_Record has logical data, and Daily_Record has integer
|> data. What I mean is - do you mean to map all the heterogenous data in
|> these types into the "storage" array? Am I missing something?
|
|In the given example, a multi-dimensional pointer to all storages of
|%temperature(3) is needed for the purpose of sum(), or that the user
|needs to accessing weekly(:)%daily(:)%hourly(:)%temperature(:) as a
|flat array. Other data are managed by the multi-level data structure,
|not a part of %storage(:,:,:,:,:). That is the minimum requirement
|based on my understanding of the given usecase. I should have
|%temperature_storage() instead of %storage() for clearity.
|
|Cheers,
|
|Jing
|>
|> Alvaro Fernandez
|> Vice President
|> Athena Technology Consultants, Inc.
|> WWW: www.athena-eng.com
|> Email: [log in to unmask]
|> Voice: 281-648-3994
|> Fax: 281-648-4015
|--
|________________________________ _-__-_-_ _-___--- _____________________
|Jing Guo, [log in to unmask], (301)614-6172(o), (301)614-6297(fx)
|Data Assimilation Office, Code 910.3, NASA/GSFC, Greenbelt, MD 20771
|
|