| File handeling architecture hints wanted [message #7781] |
Wed, 15 January 1997 00:00 |
Runar Joergensen
Messages: 3
Registered: September 1996
|
Junior Member |
|
|
Do someone have an idea how to build, maintain and explore an
dynamic data file architecture?
I'll elaborate a little more. My data is buried deep down in a dynamic
file structure. Since this structure is changing, I need my IDL
application to be able to follow/exploit new directories and appended
files. It's not very dynamic, but changes, i.e. is extended, a couple
of times during the year. Just enough so that maintaining hard coded
directory paths would be a pain in the ... The structure looks
something like this:
|-ss1 - ..
| |- mm1 - datafiles
root--|-ss2 ----- yy1 -|- mm2 - datafiles
| |
| |- yy2 -..
: :
: : |- mm1 - datafiles
: : |- mm2 - datafiles
: |- yyn -|
: :
| |- mmn - datafiles
|-ssn-1 -..
| |- mm1 - datafiles
|-ssn ----- yy1 -|- mm2 - datafiles
: :
| |- mmn - datafiles
|
|- yy2 -..
:
: |- mm1 - datafiles
: |- mm2 - datafiles
|- yyn -|
:
|- mmn - datafiles
Thus, I need to select on three levels, ss*, yy* and mm* to
find the actual datafiles. Now, I thought of a nested structure
architecture (three levels), and I've implemented something that gives me
access to the datafiles through
file=ss().yy().mm().file
I works, but this solution requires that I know a lot about the structure
to be able to access it. Any better architectures?
Thanks in advance.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=-=-=-=-=-
Runar Jorgensen ||
University of Oslo || Phone: +47 2285 5664
Department of Physics || Telefax: +47 2285 5671
P.O.Box 1048 Blindern || email: runar.jorgensen@fys.uio.no
0313 Oslo; Norway ||
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -=-=-=-=-=-=-=-
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
