The Library of Medium Resolution Spectra
| Top | Structure | Keywords |
Structure of the archive
1. The structure of the archive follows the concepts developped for the other
catalogues in HyperLeda.
Given the size of the Library (several Go), it is yet not clear if
it will be possible to mirror it on every site.
- The library is divided into different archive corresponding to
the different datasets. Each of these archives are maintained on a disk
attached to a machine connected to internet.
They are stored as tar files.
- The updating procedure of HyperLeda check every day the date
of these files, and upload those recently modified. The frames are then
checked for its conformity and re-packed into a archives available for
distribution to the mirrors
- The mirror asynchroneously update themselves to this source
2. At present, the disk storage requested to start with this project
(we will archive 1000 files of 1Mo) is:
|Developpement of the archive ||galaxies or cumulus || 1+1 Go
|Inclusion in HyperLeda ||galaxies|| 1+1 Go
|Mirror on cumulus||cumulus|| 1 Go
3. The files are stored in the gzipped FITS format. The filenames are chosen
to be unique.
The archive will be divided in subdirectories in order to avoid problems
with some unix commands which have a limitation in the size of the argument or
number of files.
The directory name codes the dataset
The file naming convention has the form:
The file name is the file number in this dataset
The following is some example how the archive tree could look like:
|L||Identifiy the archive block (L for Lyon) dataset
|YY||Calendar year for the dataset
|MM||Ordinal number of a calendar month
|i||Identification of the dataset in the observing run (1 digit)
|OB||Code for the observatory (eg. HP for Observatoire de Haute-Provence
|j||Number describing the telescope used
|nnnn||Identification number of the file, the fits.gz
extension is omitted when referencing the frames in HyperLeda, but is exists
archive_root -- 95071ESO1/
Each directory in this tree must contains a AAAReadMe.txt file.
These file are writen in free format and are not (yet) indended for
any automatic processing... but it is advised to follow as far as possible
a template taken for already existing files, in order to define a standard
which could be, in the future, used by automatic procedures.