ODR Caldata User Guide



Brief Description on the options

Below is a brief description on what each option does.

0)Data Size [bytes] – This controls the finite size of each chuck of the data.

1)Number of outstanding messages –

2)run time [seconds] – This controls the length of time the data is written to disk/RAM.

3)Dump data to screen – This allows you to output the data to screen instead of writing to disk/RAM. To dump data to disk/RAM, change the option to 0. To dumps data to screen, change the option to 1.

4)Grouping –

5)Nr IO threads –

6)Dump data to disk – Allows you to control dumping data to RAM or Disk. 0 = RAM and 1 = Disk.

NOTE: When running caldata in Dump Data To Disk mode, the program writes files to the disk. These files are not automatically deleted by caldata after the run. So you must delete these files before the next run. Due to the large quantity of these files, a simple export script has been written and has been saved under "rmall" to remove these data_io*.000000 files. To run "rmall", first exit caldata (refer to option 16), then from the terminal, execute it by typing "./rmall". This will clear the folder of all data_io*.oooooo files.

7)DMA1/2/3 [0/1/2] –

8)Word to extract –

9)DG/Network [0/1] –

10)Active Channel(s) 0/1 off/on –

11)Number of DMA buffers –

12)Number of mem pages/DMA buff –

13)Event grouping –

14)DMA debug –

15)TX next msg –

16)Run – Allows you to run the program. Just enter 16.

17)Quit – Allows you to quit the program. Just enter 17. If the program has successfully quited, you will be greeted with the following message: -

Goodbye

Initializing Caldata with various options

To run caldata, you need to login to the machine which has the ODR card installed. You must also make sure the driver to the ODR card is installed. Please refer to the ODR Driver documentation on how to compile and initialize the driver.

Once driver is loaded, you must "cd" to where the caldata files are located. Run caldata with the following command "./caldata". As the program starts up, you will be presented with 18 options. They are as following: -

   0) Data size [bytes] 2600
   1) Number of outstanding messages 1
   2) run time [seconds] 20
   3) Dump data to screen 0
   4) Grouping 10000
   5) Nr IO threads 1
   6) Dump data on disk 0
   7) DMA1/2/3 [0/1/2] 0
   8) Word to extract 6
   9) DG/Network [0/1] 0
   10) Active Channel(s) 0/1 off/on 1
   11) Number of dma buffers:  110
   12) Number of mem pages/dma buff: 80
   13) Event grouping 0
   14) DMA debug 0
   15) TX next msg 0
   16) Run 0
   17) Quit 0

Select option (number) followed by its value:

In order to change the default values of any of the options, you simply type the following when

Select option (number) followed by its value:
is printed to the screen.

For example; To change the Data Size, you type "0 3800" and press Return on the keyboard. In the terminal, it will look something like this: -

Select option (number) followed by its value: 0 3800
And so there will be another message printed to the screen with the amended data size. The message will look something like this: -

   0) Data size [bytes] 3800
   1) Number of outstanding messages 1
   2) run time [seconds] 20
   3) Dump data to screen 0
   4) Grouping 10000
   5) Nr IO threads 1
   6) Dump data on disk 0
   7) DMA1/2/3 [0/1/2] 0
   8) Word to extract 6
   9) DG/Network [0/1] 0
   10) Active Channel(s) 0/1 off/on 1
   11) Number of dma buffers:  110
   12) Number of mem pages/dma buff: 80
   13) Event grouping 0
   14) DMA debug 0
   15) TX next msg 0
   16) Run 0
   17) Quit 0

Select option (number) followed by its value:

As you can now see, the value for the Data Size [bytes] is 3800. you may also change multiple options in one go. This can be achieved by entering a space after each value. This is shown below: -

Select option (number) followed by its value: 0 1024 2 60

This refers to the Data size changed to 1024 bytes and the Run Time changed to 60 seconds.

To start the test, enter "16".

Select option (number) followed by its value: 16


Log Files of caldata

Currently caldata is programmed to output 2 different log file during each run. You may also program caldata to output additional information. To do this, please refer to the ODR Caldata Description.

  • The first log file is called caldata.log. This is saved in the directory where all the files are located for caldata. caldata.log contains all kinds of informations on the run it just performed. Informations such as : -
    • Initial parameters
    • The rate at which data was transfered
    • Number of Active loops
    • Requester Thread usage
    • Page usage statistics
    • IO thread usage.

  • The second log file is called vishal.log. This file contains information the following information: -
    • Data Size [bytes]
    • DMA Buffers
    • Memory page / DMA Buffer
    • Time [s]
    • Rate[MB/s]

This information is used to do various plots, which helps decide the optimum running parameters for caldata.


-- BarryGreen - 30-Mar-2010

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2010-03-30 - BarryGreen
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    CALICE All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback