Difference: TestBeamDataInfo (1 vs. 15)

Revision 152014-10-27 - PaoloGandini

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 134 to 134
 
META FILEATTACHMENT attachment="DUT_telescope_correlation.png" attr="" comment="" date="1406811463" name="DUT_telescope_correlation.png" path="DUT_telescope_correlation.png" size="61222" user="mpetruzz" version="1"
META FILEATTACHMENT attachment="SignalPlots.png" attr="" comment="" date="1406930333" name="SignalPlots.png" path="SignalPlots.png" size="24251" user="sblusk" version="1"
META FILEATTACHMENT attachment="RunNumbersBackup3-8-14.pdf" attr="" comment="" date="1407017122" name="RunNumbersBackup3-8-14.pdf" path="RunNumbersBackup3-8-14.pdf" size="329962" user="adavis" version="1"
Added:
>
>
META FILEATTACHMENT attachment="testbeam_Oct2014.zip" attr="" comment="Pictures of October2014 testbeam" date="1414426601" name="testbeam_Oct2014.zip" path="testbeam_Oct2014.zip" size="42668782" user="pgandini" version="1"

Revision 142014-08-03 - AdamDavis

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 120 to 120
 
Added:
>
>
 -- AdamDavis - 23 Jul 2014

Plots from test beam

Line: 132 to 133
 
META FILEATTACHMENT attachment="RunNumbersBackup30-7-14.pdf" attr="" comment="" date="1406676685" name="RunNumbersBackup30-7-14.pdf" path="RunNumbersBackup30-7-14.pdf" size="359264" user="adavis" version="1"
META FILEATTACHMENT attachment="DUT_telescope_correlation.png" attr="" comment="" date="1406811463" name="DUT_telescope_correlation.png" path="DUT_telescope_correlation.png" size="61222" user="mpetruzz" version="1"
META FILEATTACHMENT attachment="SignalPlots.png" attr="" comment="" date="1406930333" name="SignalPlots.png" path="SignalPlots.png" size="24251" user="sblusk" version="1"
Added:
>
>
META FILEATTACHMENT attachment="RunNumbersBackup3-8-14.pdf" attr="" comment="" date="1407017122" name="RunNumbersBackup3-8-14.pdf" path="RunNumbersBackup3-8-14.pdf" size="329962" user="adavis" version="1"

Revision 132014-08-02 - AdamDavis

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Revision 122014-08-02 - StevenBlusk

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 123 to 123
 -- AdamDavis - 23 Jul 2014
Changed:
<
<

First observation of correlation between DUT and telescope hits

In run "/29_07/run_000016_2907_1950.ali" (from DUT) and "Run1062" (from telescope) , correlation between hits as been observed.

The plot shows the y-position of the hit in the DUT(UT) versus the y-position of the hit in the last telescope plane (the one closest to the DUT)

>
>

Plots from test beam

 
META FILEATTACHMENT attachment="alibava_startup.png" attr="" comment="" date="1406149496" name="alibava_startup.png" path="alibava_startup.png" size="285474" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_log_data.png" attr="" comment="" date="1406149861" name="alibava_gui_log_data.png" path="alibava_gui_log_data.png" size="208657" user="adavis" version="1"
Line: 137 to 132
 
META FILEATTACHMENT attachment="RunNumbersBackup29-7-14.pdf" attr="" comment="" date="1406590439" name="RunNumbersBackup29-7-14.pdf" path="RunNumbersBackup29-7-14.pdf" size="357748" user="adavis" version="1"
META FILEATTACHMENT attachment="RunNumbersBackup30-7-14.pdf" attr="" comment="" date="1406676685" name="RunNumbersBackup30-7-14.pdf" path="RunNumbersBackup30-7-14.pdf" size="359264" user="adavis" version="1"
META FILEATTACHMENT attachment="DUT_telescope_correlation.png" attr="" comment="" date="1406811463" name="DUT_telescope_correlation.png" path="DUT_telescope_correlation.png" size="61222" user="mpetruzz" version="1"
Added:
>
>
META FILEATTACHMENT attachment="SignalPlots.png" attr="" comment="" date="1406930333" name="SignalPlots.png" path="SignalPlots.png" size="24251" user="sblusk" version="1"

Revision 112014-07-31 - MarcoPetruzzo

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 122 to 122
  -- AdamDavis - 23 Jul 2014
Added:
>
>

First observation of correlation between DUT and telescope hits

In run "/29_07/run_000016_2907_1950.ali" (from DUT) and "Run1062" (from telescope) , correlation between hits as been observed.

The plot shows the y-position of the hit in the DUT(UT) versus the y-position of the hit in the last telescope plane (the one closest to the DUT)

 
META FILEATTACHMENT attachment="alibava_startup.png" attr="" comment="" date="1406149496" name="alibava_startup.png" path="alibava_startup.png" size="285474" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_log_data.png" attr="" comment="" date="1406149861" name="alibava_gui_log_data.png" path="alibava_gui_log_data.png" size="208657" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_start_loggin.png" attr="" comment="" date="1406150029" name="alibava_gui_start_loggin.png" path="alibava_gui_start_loggin.png" size="312993" user="adavis" version="2"
META FILEATTACHMENT attachment="RunNumbersBackup29-7-14.pdf" attr="" comment="" date="1406590439" name="RunNumbersBackup29-7-14.pdf" path="RunNumbersBackup29-7-14.pdf" size="357748" user="adavis" version="1"
META FILEATTACHMENT attachment="RunNumbersBackup30-7-14.pdf" attr="" comment="" date="1406676685" name="RunNumbersBackup30-7-14.pdf" path="RunNumbersBackup30-7-14.pdf" size="359264" user="adavis" version="1"
Added:
>
>
META FILEATTACHMENT attachment="DUT_telescope_correlation.png" attr="" comment="" date="1406811463" name="DUT_telescope_correlation.png" path="DUT_telescope_correlation.png" size="61222" user="mpetruzz" version="1"

Revision 102014-07-31 - PaoloGandini

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 100 to 100
 
Added:
>
>
  • Suggested monitoring plots:https://docs.google.com/document/d/1uuvthlWSbAzHEYQ4K5hqyaFbcwPrY5R3F-NzsflN1zw/edit?usp=sharing
 
  • Be sure to ask the VELO colleague about their run number, especially if you haven't done it yet!
  • Make sure to change the file for the next run.

Revision 92014-07-30 - FedericaLionetto

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 102 to 102
 
Added:
>
>

Offline analysis

Some information on offline analysis can be found here: TbOfflineAnalysis

 

Help During a Run

If you absolutely need help, send an e-mail to lhcb-UT-testbeam@cernNOSPAMPLEASE.ch. Someone will be available to help.

Revision 82014-07-30 - AdamDavis

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 113 to 112
 This is a list of daily backups of the online run log, in case things go wrong.

Added:
>
>
 -- AdamDavis - 23 Jul 2014

META FILEATTACHMENT attachment="alibava_startup.png" attr="" comment="" date="1406149496" name="alibava_startup.png" path="alibava_startup.png" size="285474" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_log_data.png" attr="" comment="" date="1406149861" name="alibava_gui_log_data.png" path="alibava_gui_log_data.png" size="208657" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_start_loggin.png" attr="" comment="" date="1406150029" name="alibava_gui_start_loggin.png" path="alibava_gui_start_loggin.png" size="312993" user="adavis" version="2"
META FILEATTACHMENT attachment="RunNumbersBackup29-7-14.pdf" attr="" comment="" date="1406590439" name="RunNumbersBackup29-7-14.pdf" path="RunNumbersBackup29-7-14.pdf" size="357748" user="adavis" version="1"
Added:
>
>
META FILEATTACHMENT attachment="RunNumbersBackup30-7-14.pdf" attr="" comment="" date="1406676685" name="RunNumbersBackup30-7-14.pdf" path="RunNumbersBackup30-7-14.pdf" size="359264" user="adavis" version="1"

Revision 72014-07-29 - MarcoPetruzzo

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 87 to 87
  When you're satisfied, click "Open". You must do this before each run, or you risk overwriting the data!!!
Added:
>
>

Telescope files directory

The telescope files are stored in the following directory:

eos/lhcb/testbeam/velo/timepix3/

 

After a run

After a run is done, make sure to:

Revision 62014-07-29 - AdamDavis

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 7 to 8
 

Information on DAQ PC (pcsyr01)

Changed:
<
<
The pcsyr01 is running SLC 6.5 Linux OS and has a large (~ 4 TB) local disk to store data files. NOTE! root and the user (tboperator) passwords are displayed on a label that is put on the machine front panel. During the data taking shifters should use the tboperator account only!
>
>
The pcsyr01 is running SLC 6.5 Linux OS and has a large (~ 4 TB) local disk to store data files. NOTE! root and the user ( tboperator) passwords are displayed on a label that is put on the machine front panel. During the data taking shifters should use the tboperator account only!
 

DAQ PC storage layout

Changed:
<
<
The DAQ machine have installed 3 physical hard drives. Two of them are small (~ 250 GB) and should not be used to store data/work/software installation. They contain OS and /home directory. The large disk is divided into three logical volumes (partitions) that are dedicated to software installation and data storage. The partitions names are as follow: /lhcb (~ 800 GB), /data1 (~ 1.5 TB) and /data2 (~ 1.5 TB). All the necessary software packages have been installed at /lhcb (Gaudi + DaVinci, Kepler, alibava). It is strongly recommended that any additional staff should be also installed there. Two remining partitions are dedicated for data files acquires during the data taking runs.
>
>
The DAQ machine have installed 3 physical hard drives. Two of them are small (~ 250 GB) and should not be used to store data/work/software installation. They contain OS and /home directory. The large disk is divided into three logical volumes (partitions) that are dedicated to software installation and data storage. The partitions names are as follow: /lhcb (~ 800 GB), /data1 (~ 1.5 TB) and /data2 (~ 1.5 TB). All the necessary software packages have been installed at /lhcb (Gaudi + DaVinci, Kepler, alibava). It is strongly recommended that any additional staff should be also installed there. Two remining partitions are dedicated for data files acquires during the data taking runs.
 

DAQ PC environment configuration

Changed:
<
<
Presently the DAQ PC can run alibava and LHCb software (Gaudi framework, DaVinci v35r0 and the latest Kepler project). It should be kept in mind that a shifter should not mix running alibava gui and LHCb applications. The reason for this is that there may be subtle differences between the local ROOT installation and the one that is used by a particular version installed together with the LHCb stack. It is strongly advised then to start from a fresh terminal in order to use the LHCb software.
>
>
Presently the DAQ PC can run alibava and LHCb software (Gaudi framework, DaVinci v35r0 and the latest Kepler project). It should be kept in mind that a shifter should not mix running alibava gui and LHCb applications. The reason for this is that there may be subtle differences between the local ROOT installation and the one that is used by a particular version installed together with the LHCb stack. It is strongly advised then to start from a fresh terminal in order to use the LHCb software.
 

Running alibava

Line: 33 to 28
  log on the DAQ machine as the tboperator (password can be found on the front panel of the machine)
Changed:
<
<
open a fresh terminal and execute:
>
>
Open the terminal. There are scripts in place which should provide you the tools necessary to run everything!

In the case of a problem, open a fresh terminal and execute:

 
Changed:
<
<
 > cd 
>
>
 > cd 
 
Changed:
<
<
 > source setlhcb 
>
>
> source setlhcb
 
Changed:
<
<
 > SetupProject DaVinci v35r0 --build-env 
(this will take you to the /lhcb/tboperator/cmtuser/DaVinci_v35r0 folder)
>
>
> SetupProject DaVinci v35r0 --build-env

(this will take you to the /lhcb/tboperator/cmtuser/DaVinci_v35r0 folder)

 
 > SetupProject DaVinci v35r0 

Line: 57 to 56
  to start the AlibavaGUI. This should bring up the main controls for Alibava.
Changed:
<
<
>
>
 

Data Format for Alibava files.

Alibava outputs many files, and in order to keep thing straight, the following convention for file type is used

Line: 70 to 69
  ped_000001_2307_1107.ali
Changed:
<
<
Additionally, for each run, there is a readme file with the same format.
>
>
Files are stored in a folder for each day, labeled as dd_mm (28_07, for example)
 
Changed:
<
<
readme_000001_2307_1107.txt
>
>
Additionally, for each run, there is a readme file in each of the folders.
  This contains all the necessary information about beam conditions, run buffer size, etc.
Line: 95 to 94
 
Added:
>
>
  • Be sure to ask the VELO colleague about their run number, especially if you haven't done it yet!
 
  • Make sure to change the file for the next run.

Help During a Run

If you absolutely need help, send an e-mail to lhcb-UT-testbeam@cernNOSPAMPLEASE.ch. Someone will be available to help.

There will be a phone to call, should something go wrong, or there is a list of numbers next to the keyboard.

Added:
>
>

Backups of online run log

This is a list of daily backups of the online run log, in case things go wrong.

 
Added:
>
>
 -- AdamDavis - 23 Jul 2014

META FILEATTACHMENT attachment="alibava_startup.png" attr="" comment="" date="1406149496" name="alibava_startup.png" path="alibava_startup.png" size="285474" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_log_data.png" attr="" comment="" date="1406149861" name="alibava_gui_log_data.png" path="alibava_gui_log_data.png" size="208657" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_start_loggin.png" attr="" comment="" date="1406150029" name="alibava_gui_start_loggin.png" path="alibava_gui_start_loggin.png" size="312993" user="adavis" version="2"
Added:
>
>
META FILEATTACHMENT attachment="RunNumbersBackup29-7-14.pdf" attr="" comment="" date="1406590439" name="RunNumbersBackup29-7-14.pdf" path="RunNumbersBackup29-7-14.pdf" size="357748" user="adavis" version="1"

Revision 52014-07-24 - TomaszSzumlak

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 7 to 7
 

Information on DAQ PC (pcsyr01)

Changed:
<
<
The pcsyr01 is running SLC 6.5 Linux OS and has a large (~ 4 TB) local disk to store data files. NOTE! root and the user (tboperator) passwords are displayed on a label that is put on the machine
>
>
The pcsyr01 is running SLC 6.5 Linux OS and has a large (~ 4 TB) local disk to store data files. NOTE! root and the user (tboperator) passwords are displayed on a label that is put on the machine
 front panel. During the data taking shifters should use the tboperator account only!
Changed:
<
<

DAQ pc storage layout

>
>

DAQ PC storage layout

  The DAQ machine have installed 3 physical hard drives. Two of them are small (~ 250 GB) and should not be used to store data/work/software installation. They contain OS and /home directory. The large disk is divided into three logical volumes (partitions) that are dedicated to software installation and data storage. The partitions names are as follow: /lhcb (~ 800 GB), /data1 (~ 1.5 TB) and /data2 (~ 1.5 TB). All the necessary software packages have been installed at /lhcb (Gaudi + DaVinci, Kepler, alibava). It is strongly recommended that any additional staff should be also installed there. Two remining partitions are dedicated for data files acquires during the data taking runs.
Changed:
<
<

DAQ pc environment configuration

>
>

DAQ PC environment configuration

 
Changed:
<
<
Presently the DAQ pc can run alibava and LHCb software (Gaudi framework, DaVinci v35r0 and the latest Kepler project). It should be kept in mind that a shifter should not mix running alibava gui and LHCb applications.
>
>
Presently the DAQ PC can run alibava and LHCb software (Gaudi framework, DaVinci v35r0 and the latest Kepler project). It should be kept in mind that a shifter should not mix running alibava gui and LHCb applications.
 The reason for this is that there may be subtle differences between the local ROOT installation and the one that is used by a particular version installed together with the LHCb stack. It is strongly advised then to start from a fresh terminal in order to use the LHCb software.
Added:
>
>

Running alibava

When starting a fresh shell a script set-ut-tb.sh will be executed by default. This will move the user to a working folder which contains symbolic links to the storage partitions /data1 and /data2 as well as link to the alibava-gui executable (for details how to run and operate the GUI see 'Starting the AlibavaGUI' below). NOTE that all necessary components needed from the ROOT will be taken from the local standalone installation (check the $ROOTSYS env variable).

Configuring the LHCb software

In order to get access to the local installation of the LHCb software do the following steps:

log on the DAQ machine as the tboperator (password can be found on the front panel of the machine)

open a fresh terminal and execute:

 > cd 

 > source setlhcb 

 > SetupProject DaVinci v35r0 --build-env 
(this will take you to the /lhcb/tboperator/cmtuser/DaVinci_v35r0 folder)

 > SetupProject DaVinci v35r0 

You are ready to go now! (The Kepler project can be set up in the similar way)

 

Logging Into the Machine

Revision 42014-07-24 - TomaszSzumlak

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Information for Shifters

Added:
>
>

Information on DAQ PC (pcsyr01)

The pcsyr01 is running SLC 6.5 Linux OS and has a large (~ 4 TB) local disk to store data files. NOTE! root and the user (tboperator) passwords are displayed on a label that is put on the machine front panel. During the data taking shifters should use the tboperator account only!

DAQ pc storage layout

The DAQ machine have installed 3 physical hard drives. Two of them are small (~ 250 GB) and should not be used to store data/work/software installation. They contain OS and /home directory. The large disk is divided into three logical volumes (partitions) that are dedicated to software installation and data storage. The partitions names are as follow: /lhcb (~ 800 GB), /data1 (~ 1.5 TB) and /data2 (~ 1.5 TB). All the necessary software packages have been installed at /lhcb (Gaudi + DaVinci, Kepler, alibava). It is strongly recommended that any additional staff should be also installed there. Two remining partitions are dedicated for data files acquires during the data taking runs.

DAQ pc environment configuration

Presently the DAQ pc can run alibava and LHCb software (Gaudi framework, DaVinci v35r0 and the latest Kepler project). It should be kept in mind that a shifter should not mix running alibava gui and LHCb applications. The reason for this is that there may be subtle differences between the local ROOT installation and the one that is used by a particular version installed together with the LHCb stack. It is strongly advised then to start from a fresh terminal in order to use the LHCb software.

 

Logging Into the Machine

As the setup has the Alibava motherboard and the connected PC inside of the control areai, you will need to ssh into the machine from the control room. Remember the -X or -Y flag. The login info is right next to the keyboard in the control room.

Revision 32014-07-24 - PaoloGandini

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Line: 51 to 51
  After a run is done, make sure to:
Changed:
<
<
  • Add a Readme file to the same directory where the pedistal and run data are.
  • Write down everything in the log book/elog
>
>
 
  • Make sure to change the file for the next run.

Help During a Run

Revision 22014-07-23 - AdamDavis

Line: 1 to 1
 
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Added:
>
>
 

Information for Shifters

Added:
>
>

Logging Into the Machine

 
Changed:
<
<

Data Format for Alibava files.

>
>
As the setup has the Alibava motherboard and the connected PC inside of the control areai, you will need to ssh into the machine from the control room. Remember the -X or -Y flag. The login info is right next to the keyboard in the control room.

Starting the AlibavaGUI

After logging into the machine, you are ready to use the AlibavaGUI. At the command prompt, type

alibava-gui

to start the AlibavaGUI. This should bring up the main controls for Alibava.

Data Format for Alibava files.

  Alibava outputs many files, and in order to keep thing straight, the following convention for file type is used
Line: 22 to 35
  This contains all the necessary information about beam conditions, run buffer size, etc.
Added:
>
>

Setting The Datafile to be Stored

In order to set the data file, click on the "LogData" button

alibava_gui_start_loggin.png

After pressing this button, you will be directed to a user dialogue to change the input file. Please do not put anything on the 250 GB disk , this is only for the operating system. You should go to data1 or data2. At the dialogue, create a run folder, and there, enter the name of the file, following the above conventions.

alibava_gui_log_data.png

When you're satisfied, click "Open". You must do this before each run, or you risk overwriting the data!!!

After a run

After a run is done, make sure to:

  • Add a Readme file to the same directory where the pedistal and run data are.
  • Write down everything in the log book/elog
  • Make sure to change the file for the next run.

Help During a Run

If you absolutely need help, send an e-mail to lhcb-UT-testbeam@cernNOSPAMPLEASE.ch. Someone will be available to help.

There will be a phone to call, should something go wrong, or there is a list of numbers next to the keyboard.

 -- AdamDavis - 23 Jul 2014
Added:
>
>
META FILEATTACHMENT attachment="alibava_startup.png" attr="" comment="" date="1406149496" name="alibava_startup.png" path="alibava_startup.png" size="285474" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_log_data.png" attr="" comment="" date="1406149861" name="alibava_gui_log_data.png" path="alibava_gui_log_data.png" size="208657" user="adavis" version="1"
META FILEATTACHMENT attachment="alibava_gui_start_loggin.png" attr="" comment="" date="1406150029" name="alibava_gui_start_loggin.png" path="alibava_gui_start_loggin.png" size="312993" user="adavis" version="2"

Revision 12014-07-23 - AdamDavis

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="SiliconStripTrackerTestbeamPage"
<!--* Set ALLOWTOPICVIEW = lhcb-general-->

UT Test Beam Datataking

Information for Shifters

Data Format for Alibava files.

Alibava outputs many files, and in order to keep thing straight, the following convention for file type is used

Run-Type_ 6-digit-Run#_Date_Time.ali

So for run 000001 and pedistals, taken July 23 2014 at 11:07 am, the data files would be

run_000001_2307_1107.ali

ped_000001_2307_1107.ali

Additionally, for each run, there is a readme file with the same format.

readme_000001_2307_1107.txt

This contains all the necessary information about beam conditions, run buffer size, etc.

-- AdamDavis - 23 Jul 2014

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