As explained in many different parts of such documentation the "crucial" connection between the Daq and the Kloe detector is carried out "in software" by the Detector Map. Surely enough, whenever stable running will be assured one and only one Dmap will be used. Still, along the time different maps will have to be downloaded.

Similarly the geovmemap has to be used offline as the list of the Boards serial numbers (useful for example for TDC Calibration purposes). Translator programs from Ascii to HTML or TCL files already exist for the Dmap.

In order to be sure the maps do not get lost or confused we propose the following:

• Store it in a safe place. Only few responsible physicists should be able to change it, correct it or update it. At the moment the disk area: /kloe/soft/maps/ with 3 subdirectories: experiment,caltest,dchtest exists and I strongly suggest to be used. Example for the Calorimeter System Test for geovmefile , dmapfile or dmapfile HTML can be seen.

• ONLINE USAGE:

  We SHOULD USE only ASCII files. If possible NO USAGE OF HEPDB in order not to load ZEBRA package inside the Online programs.

  The current version should have a plain-name as for example: dmapfile, geovmefile or board_ser_num. The version changing along the time should instead have a run_number inserted in the name. For istance, dmapfile_run_1, dmapfile_run_100 and so on. Thumb rule is as follows:

  The dmapfile_run_1 will be the valid one from 1 to 99, the second one from 100 to infinity.

• OFFLINE USAGE AT THE MOMENT:

  To use it Offline we can always run the existing software and use the word dmapfile as a symbolic link to be present in the running directory. This is what we are doing at the moment. Example of usage of the Dmap are many both Online than Offline we refer here to the offline ones:

  • setup tls development
  • less K$TLS/ref/raw2ntu.kloe
  This module translates automatically the DAQ format in a CWNtuple both for KLOE calorimeter. Easy extention to chamber and quadrupoles is foreseen if the appropriate Dmaps will be given. Trigger is more difficult at the moment, since the DMAP is not yet implement for this detector.

• FUTURE USAGE OFFLINE:

  We would like to store these objects (maps) also as FZ files in HEPDB for a more stable Offline usage. At run_init the maps are read from HEPDB and copied as ascii-files in the executable working directory, thus avoiding any possible conflict with old or previously used map-versions. One and only one A_C module (DMAP_LOADER) should access the maps opening and loading it. All the other modules should just use the information trough calls to DMAP_GET or similia.