https://clonwiki0.jlab.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=129.57.76.146CLONWiki - User contributions [en]2026-04-08T03:37:56ZUser contributionsMediaWiki 1.42.1https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4895Data Monitor2010-07-20T14:45:38Z<p>129.57.76.146: /* to do */</p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== to do ==<br />
<br />
Sergey: Moscow cell phone: 9-011-7-916-729-8203, skype: boiarino<br />
<br />
1. Normalization:<br />
<br />
* on reference (current algorithm)<br />
<br />
* on the naighbors of the same kind<br />
<br />
* on the same object in another sector(s), probably averaging 6 or 5 sectors, or averaging 3 sectors with medium counts etc<br />
<br />
* if running without beam (cosmic) for long time, should recognize it and give ONE warning for entire DC<br />
<br />
<br />
2. Reporting:<br />
<br />
* warning messages (hot channels (50% up, 120% down etc); if up more then 300% up, discuss with Mac<br />
<br />
* error messages: sharp drop (almost to zero, maybe 90%)<br />
<br />
* any unusual effects - discuss with Mac<br />
<br />
<br />
3. Results:<br />
<br />
* program<br />
<br />
* wiki manual with algorithm description<br />
<br />
== Juan's work ==<br />
<br />
The file juanlib.c analyzes data from drift chamber wires to determine whether there exists a hardware malfunction within the drift chamber. After 90,000 events (~30 seconds) the program stores the hits from each wire into 6x6 groups designated by sector, superlayer, and wire number. Using these groups as a reference, the program can look at future events to scan for alarming activity. <br />
<br />
<br />
At the 180,000 event mark and for every 90,000 events afterward, the program compares the past 90,000 events with the reference to determine whether suspicious activity occurs. Any 6x6 group that changes by 60% or more, with respect to the reference, is marked as an error. The 60% threshold was determined by trial and error on many data sets. A drop of roughly 60% across all regions generally corresponds to a drop in beam current. Errors are stored in a separate data structure named errorlist.<br />
<br />
<br />
Alarms are only sent if greater than 5 errors occur and only if they occur within the same sector. This was implemented due to small inconsistencies with beam current leading to small regions being flagged as errors. If 5 or more of these errors fall within the same superlayer only a superlayer alarm will occur, rather than multiple 6x6 alarms. If greater than 100 errors are recorded, only an alarm warning that major drops are found in many areas will appear. This type of alarm usually corresponds to a drop in beam current.<br />
<br />
<br />
Juanlib.c also creates histogram files from the data collected. Marked as 101-106, 201-206 and 301-306, these plots correspond to data from the 6 respective sectors. Histograms 101-106 correspond to one dimensional histograms, 201-206 to two dimensional histograms (hits in wire and layer), and 301-306 to normalized changes in 6x6 groups with respect to the reference. The box feature is recommended for the 301-306 plots.<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping<br />
<br />
* ADB mapping<br />
<br />
== dmlib.c algorithm ==<br />
<br />
So-called 'tree' is used to obtain all sets which suppose to be filled using particular data channel.<br />
<br />
BankID->BankNumber->HighID->LowID->Place</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4894Data Monitor2010-07-20T14:39:58Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== to do ==<br />
<br />
Sergey (Moscow): <br />
<br />
1. Normalization:<br />
<br />
* on reference (current algorithm)<br />
<br />
* on the naighbors of the same kind<br />
<br />
* on the same object in another sector(s), probably averaging 6 or 5 sectors, or averaging 3 sectors with medium counts etc<br />
<br />
* if running without beam (cosmic) for long time, should recognize it and give ONE warning for entire DC<br />
<br />
<br />
2. Reporting:<br />
<br />
* warning messages (hot channels (50% up, 120% down etc); if up more then 300% up, discuss with Mac<br />
<br />
* error messages: sharp drop (almost to zero, maybe 90%)<br />
<br />
* any unusual effects - discuss with Mac<br />
<br />
<br />
3. Results:<br />
<br />
* program<br />
<br />
* wiki manual with algorithm description<br />
<br />
<br />
<br />
<br />
== Juan's work ==<br />
<br />
The file juanlib.c analyzes data from drift chamber wires to determine whether there exists a hardware malfunction within the drift chamber. After 90,000 events (~30 seconds) the program stores the hits from each wire into 6x6 groups designated by sector, superlayer, and wire number. Using these groups as a reference, the program can look at future events to scan for alarming activity. <br />
<br />
<br />
At the 180,000 event mark and for every 90,000 events afterward, the program compares the past 90,000 events with the reference to determine whether suspicious activity occurs. Any 6x6 group that changes by 60% or more, with respect to the reference, is marked as an error. The 60% threshold was determined by trial and error on many data sets. A drop of roughly 60% across all regions generally corresponds to a drop in beam current. Errors are stored in a separate data structure named errorlist.<br />
<br />
<br />
Alarms are only sent if greater than 5 errors occur and only if they occur within the same sector. This was implemented due to small inconsistencies with beam current leading to small regions being flagged as errors. If 5 or more of these errors fall within the same superlayer only a superlayer alarm will occur, rather than multiple 6x6 alarms. If greater than 100 errors are recorded, only an alarm warning that major drops are found in many areas will appear. This type of alarm usually corresponds to a drop in beam current.<br />
<br />
<br />
Juanlib.c also creates histogram files from the data collected. Marked as 101-106, 201-206 and 301-306, these plots correspond to data from the 6 respective sectors. Histograms 101-106 correspond to one dimensional histograms, 201-206 to two dimensional histograms (hits in wire and layer), and 301-306 to normalized changes in 6x6 groups with respect to the reference. The box feature is recommended for the 301-306 plots.<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping<br />
<br />
* ADB mapping<br />
<br />
== dmlib.c algorithm ==<br />
<br />
So-called 'tree' is used to obtain all sets which suppose to be filled using particular data channel.<br />
<br />
BankID->BankNumber->HighID->LowID->Place</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4893Data Monitor2010-07-20T14:39:40Z<p>129.57.76.146: /* to do */</p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== to do ==<br />
<br />
Sergey (Moscow): <br />
<br />
1. Normalization:<br />
<br />
* on reference (current algorithm)<br />
<br />
* on the naighbors of the same kind<br />
<br />
* on the same object in another sector(s), probably averaging 6 or 5 sectors, or averaging 3 sectors with medium counts etc<br />
<br />
* if running without beam (cosmic) for long time, should recognize it and give ONE warning for entire DC<br />
<br />
<br />
2. Reporting:<br />
<br />
* warning messages (hot channels (50% up, 120% down etc); if up more then 300% up, discuss with Mac<br />
<br />
* error messages: sharp drop (almost to zero, maybe 90%)<br />
<br />
* any unusual effects - discuss with Mac<br />
<br />
<br />
3. Results:<br />
<br />
* program<br />
<br />
* wiki manual with algorithm description<br />
<br />
== Juan's work ==<br />
<br />
The file juanlib.c analyzes data from drift chamber wires to determine whether there exists a hardware malfunction within the drift chamber. After 90,000 events (~30 seconds) the program stores the hits from each wire into 6x6 groups designated by sector, superlayer, and wire number. Using these groups as a reference, the program can look at future events to scan for alarming activity. <br />
<br />
<br />
At the 180,000 event mark and for every 90,000 events afterward, the program compares the past 90,000 events with the reference to determine whether suspicious activity occurs. Any 6x6 group that changes by 60% or more, with respect to the reference, is marked as an error. The 60% threshold was determined by trial and error on many data sets. A drop of roughly 60% across all regions generally corresponds to a drop in beam current. Errors are stored in a separate data structure named errorlist.<br />
<br />
<br />
Alarms are only sent if greater than 5 errors occur and only if they occur within the same sector. This was implemented due to small inconsistencies with beam current leading to small regions being flagged as errors. If 5 or more of these errors fall within the same superlayer only a superlayer alarm will occur, rather than multiple 6x6 alarms. If greater than 100 errors are recorded, only an alarm warning that major drops are found in many areas will appear. This type of alarm usually corresponds to a drop in beam current.<br />
<br />
<br />
Juanlib.c also creates histogram files from the data collected. Marked as 101-106, 201-206 and 301-306, these plots correspond to data from the 6 respective sectors. Histograms 101-106 correspond to one dimensional histograms, 201-206 to two dimensional histograms (hits in wire and layer), and 301-306 to normalized changes in 6x6 groups with respect to the reference. The box feature is recommended for the 301-306 plots.<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping<br />
<br />
* ADB mapping<br />
<br />
== dmlib.c algorithm ==<br />
<br />
So-called 'tree' is used to obtain all sets which suppose to be filled using particular data channel.<br />
<br />
BankID->BankNumber->HighID->LowID->Place</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4892Data Monitor2010-07-20T14:14:43Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== to do ==<br />
<br />
1. Normalization:<br />
<br />
* on reference (current algorithm)<br />
<br />
* on the naighbors of the same kind<br />
<br />
* on the same object in another sector(s), probably averaging 6 or 5 sectors, or averaging 3 sectors with medium counts etc<br />
<br />
2. Reporting:<br />
<br />
* warning messages (hot channels (50% up, 120% down etc)<br />
<br />
<br />
== Juan's work ==<br />
<br />
The file juanlib.c analyzes data from drift chamber wires to determine whether there exists a hardware malfunction within the drift chamber. After 90,000 events (~30 seconds) the program stores the hits from each wire into 6x6 groups designated by sector, superlayer, and wire number. Using these groups as a reference, the program can look at future events to scan for alarming activity. <br />
<br />
<br />
At the 180,000 event mark and for every 90,000 events afterward, the program compares the past 90,000 events with the reference to determine whether suspicious activity occurs. Any 6x6 group that changes by 60% or more, with respect to the reference, is marked as an error. The 60% threshold was determined by trial and error on many data sets. A drop of roughly 60% across all regions generally corresponds to a drop in beam current. Errors are stored in a separate data structure named errorlist.<br />
<br />
<br />
Alarms are only sent if greater than 5 errors occur and only if they occur within the same sector. This was implemented due to small inconsistencies with beam current leading to small regions being flagged as errors. If 5 or more of these errors fall within the same superlayer only a superlayer alarm will occur, rather than multiple 6x6 alarms. If greater than 100 errors are recorded, only an alarm warning that major drops are found in many areas will appear. This type of alarm usually corresponds to a drop in beam current.<br />
<br />
<br />
Juanlib.c also creates histogram files from the data collected. Marked as 101-106, 201-206 and 301-306, these plots correspond to data from the 6 respective sectors. Histograms 101-106 correspond to one dimensional histograms, 201-206 to two dimensional histograms (hits in wire and layer), and 301-306 to normalized changes in 6x6 groups with respect to the reference. The box feature is recommended for the 301-306 plots.<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping<br />
<br />
* ADB mapping<br />
<br />
== dmlib.c algorithm ==<br />
<br />
So-called 'tree' is used to obtain all sets which suppose to be filled using particular data channel.<br />
<br />
BankID->BankNumber->HighID->LowID->Place</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=SSH&diff=4868SSH2010-07-19T16:50:35Z<p>129.57.76.146: </p>
<hr />
<div>First, enable X11 forwarding: uncommented and properly set 2 following lines in ''/etc/ssh/ssh_config'' file: <br />
<br />
Host *<br />
ForwardX11 yes<br />
<br />
Normally ''ssh'' creates ''.Xauthority'' file in ''$HOME'' directory. If ''$HOME'' directory is on file server and shared between different machines, it can be a conflict. It is recommended in that case to tell ''ssh'' to place ''.Xauthority'' file somewhere else, for example in ''/tmp'' directory which is usually local. Do following:<br />
<br />
1. Uncomment or add following line in ''/etc/ssh/sshd_config'' (it will force execution of /etc/ssh/sshrc script which we'll create below; also every user's $HOME/.ssh/environment file will be processed):<br />
<br />
PermitUserEnvironment yes<br />
<br />
2. Add two lines in ''/etc/profile'':<br />
<br />
XAUTHORITY=/tmp/.Xauthority.$LOGNAME<br />
export XAUTHORITY<br />
<br />
3. Create ''/etc/ssh/sshrc'' with following contents:<br />
<br />
HOME=/tmp<br />
XAUTHORITY=$HOME/.Xauthority.$USER<br />
export XAUTHORITY<br />
if read proto cookie && [ -n "$DISPLAY" ]<br />
then<br />
if [ `echo $DISPLAY | cut -c1-10` = 'localhost:' ]<br />
then<br />
# X11UseLocalhost=yes<br />
echo add unix:`echo $DISPLAY |<br />
cut -c11-` $proto $cookie<br />
else<br />
# X11UseLocalhost=no<br />
echo add $DISPLAY $proto $cookie<br />
fi | /usr/openwin/bin/xauth -q -<br />
fi<br />
<br />
(on RHEL4 ''xauth'' is located at ''/usr/X11R6/bin/xauth'', on RHEL5 at ''/usr/bin'', adjust script accordingly)<br />
<br />
4. Create ''/root/.ssh/environment'' file with following contents:<br />
<br />
XAUTHORITY=/tmp/.Xauthority.root<br />
<br />
5. NOTIFY ALL USERS TO HAVE THAT FILE WITH CORRESPONDING CONTENTS IN THEIR ''$HOME/.ssh'' directories. You can do it for example by placing following into ''/etc/.login'' (on linux you can use ''/etc/csh.login''):<br />
<br />
if (! -e ~/.ssh/environment ) then<br />
echo ""<br />
echo "===== ERROR: create file '~/.ssh/environment' containing following line:"<br />
echo "===== XAUTHORITY=/tmp/.Xauthority.$LOGNAME"<br />
echo "===== OTHERWISE SSH/X11 MAY NOT WORK PROPERLY"<br />
echo ""<br />
endif<br />
<br />
<br />
6. Restart ssh service by<br />
<br />
svcadm restart network/ssh<br />
<br />
(on Linux ''/etc/init.d/sshd restart'')<br />
<br />
7. If need to make ssh without password between different clon machines for some user, login as that user and do following:<br />
cd .ssh<br />
ssh-keygen -t rsa<br />
<hit return on password prompt><br />
cp id_rsa.pub authorized_keys</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=July_7,_2010_online_meeting_minutes&diff=4857July 7, 2010 online meeting minutes2010-07-07T15:31:11Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Nerses Gevorgyan<br />
<br />
1. Run status<br />
<br />
internal dipol target magnet broke (wire broke somewhere), hope to fix by<br />
next week<br />
<br />
DC10 - will replace crate, because all other components were replaced already<br />
<br />
polar - print messages, must investigate<br />
<br />
2. Other sfuff<br />
<br />
CTOF - need scope with ethernet, need translation table for ADCs (same board<br />
as Start counter)<br />
<br />
PRIMEX - Pawel is fixing FASTBUS power supplies, I'm geting ready to run DAQ<br />
<br />
EPICS/nerses: harpscan still need work, suspect TCL, will check; when fixed,<br />
will replace clon02; check clon01 cron jobs under epics; old clon01 may be<br />
needed for XRTgraph, will be addressed in EDM - first EDM app will be tagger<br />
histograms<br />
<br />
JLAB discr - under testing, so far so good, nore tests will be done<br />
<br />
NOTE: move gas, need space for VME !!!!!</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=July_7,_2010_online_meeting_minutes&diff=4856July 7, 2010 online meeting minutes2010-07-07T15:30:57Z<p>129.57.76.146: </p>
<hr />
<div>July 7, 2010: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Nerses Gevorgyan<br />
<br />
1. Run status<br />
<br />
internal dipol target magnet broke (wire broke somewhere), hope to fix by<br />
next week<br />
<br />
DC10 - will replace crate, because all other components were replaced already<br />
<br />
polar - print messages, must investigate<br />
<br />
2. Other sfuff<br />
<br />
CTOF - need scope with ethernet, need translation table for ADCs (same board<br />
as Start counter)<br />
<br />
PRIMEX - Pawel is fixing FASTBUS power supplies, I'm geting ready to run DAQ<br />
<br />
EPICS/nerses: harpscan still need work, suspect TCL, will check; when fixed,<br />
will replace clon02; check clon01 cron jobs under epics; old clon01 may be<br />
needed for XRTgraph, will be addressed in EDM - first EDM app will be tagger<br />
histograms<br />
<br />
JLAB discr - under testing, so far so good, nore tests will be done<br />
<br />
NOTE: move gas, need space for VME !!!!!</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_July_7,_2010&diff=4855CLON meeting July 7, 20102010-07-07T15:29:24Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, July 7 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current run status<br />
<br />
2. Other activities (discr testing, CTOF test, PRIMEX preparations etc)</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=4854CLON Group Meetings2010-07-07T15:28:26Z<p>129.57.76.146: /* 2010 */</p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
== 2007 ==<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
== 2008 ==<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]<br />
<br />
== 2009 ==<br />
<br />
[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 2, 2009]] >>>>> [[September 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 23, 2009]] >>>>> [[September 23, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 30, 2009]] >>>>> [[September 30, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting October 14, 2009]] >>>>> [[October 14, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting November 11, 2009]] >>>>> [[November 11, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 2, 2009]] >>>>> [[December 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 16, 2009]] >>>>> [[December 16, 2009 online meeting minutes]]<br />
<br />
== 2010 ==<br />
<br />
[[CLON meeting January 13, 2010]] >>>>> [[January 13, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting January 27, 2010]] >>>>> [[January 27, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 10, 2010]] >>>>> [[February 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 24, 2010]] >>>>> [[February 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 10, 2010]] >>>>> [[March 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 17, 2010]] >>>>> [[March 17, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 24, 2010]] >>>>> [[March 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 7, 2010]] >>>>> [[April 7, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 21, 2010]] >>>>> [[April 21, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 5, 2010]] >>>>> [[May 5, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 12, 2010]] >>>>> [[May 12, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 26, 2010]] >>>>> [[May 26, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting June 9, 2010]] >>>>> [[June 9, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting June 16, 2010]] >>>>> [[June 16, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting July 7, 2010]] >>>>> [[July 7, 2010 online meeting minutes]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4853Data Monitor2010-06-28T15:07:25Z<p>129.57.76.146: /* Drift Chamber Hardware Mapping */</p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping<br />
<br />
* ADB mapping</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4852Data Monitor2010-06-28T15:07:03Z<p>129.57.76.146: /* Drift Chamber Hardware Mapping */</p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== Drift Chamber Hardware Mapping ==<br />
<br />
* TDC mapping<br />
<br />
* Low voltage mapping<br />
<br />
* fuses mapping<br />
<br />
* HV mapping</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4851Data Monitor2010-06-28T15:06:10Z<p>129.57.76.146: /* Drift Chamber HArdware Mapping */</p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== Drift Chamber Hardware Mapping ==</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4850Data Monitor2010-06-28T15:06:00Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].<br />
<br />
== Drift Chamber HArdware Mapping ==</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4849Data Monitor2010-06-28T15:05:07Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [[ET System]].</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4848Data Monitor2010-06-28T15:04:56Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the [ET System].</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Data_Monitor&diff=4847Data Monitor2010-06-28T15:04:23Z<p>129.57.76.146: </p>
<hr />
<div>'''Data Monitor''' is the data quality check program. It runs online being attached to the ET system.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLAS_Online_Software&diff=4846CLAS Online Software2010-06-28T15:02:59Z<p>129.57.76.146: </p>
<hr />
<div>'''If you want information about DAQ/Online Systems startup and recover procedures, use following link:'''<br />
<br />
[[DAQ/Online Quick Reference]]<br />
<br />
[[DAQ/Online Software Stricture]]<br />
<br />
<br />
'''Wolfram test setup'''<br />
<br />
* NOTE: EXPID must be clasdev, SESSION must be claswolf<br />
<br />
* serial connection to the VME crate: on wolfram: ''cu -l /dev/cua/b''<br />
<br />
* to start DAQ:<br />
ssh vpk@clon00<br />
wolfram_start<br />
<br />
* to start ROOT:<br />
ssh vpk@clon00<br />
cmroot claswolf hist_claswolf<br />
<br />
* to kill DAQ:<br />
wolfram_exit<br />
<br />
<br />
'''Expert Information:'''<br />
<br />
[[ADC Pedestals Measurement Procedure]]<br />
<br />
[[Alarm Browser]]<br />
<br />
[[Alarm Server]]<br />
<br />
[[Data Monitor]]<br />
<br />
[[dbrouter]]<br />
<br />
[[Epics Server]]<br />
<br />
[[ET System]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[info_server]]<br />
<br />
[[Logbook]]<br />
<br />
[[msql database]]<br />
<br />
[[Process Management]]<br />
<br />
[[Recsis]]<br />
<br />
[[sgutil]]<br />
<br />
[[Stadis]]<br />
<br />
[[CMON]] CLAS Online Data Monitoring<br />
<br />
[[Runlog]] programs</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLAS_Online_Software&diff=4845CLAS Online Software2010-06-28T15:02:40Z<p>129.57.76.146: </p>
<hr />
<div>'''If you want information about DAQ/Online Systems startup and recover procedures, use following link:'''<br />
<br />
[[DAQ/Online Quick Reference]]<br />
<br />
[[DAQ/Online Software Stricture]]<br />
<br />
<br />
'''Wolfram test setup'''<br />
<br />
* NOTE: EXPID must be clasdev, SESSION must be claswolf<br />
<br />
* serial connection to the VME crate: on wolfram: ''cu -l /dev/cua/b''<br />
<br />
* to start DAQ:<br />
ssh vpk@clon00<br />
wolfram_start<br />
<br />
* to start ROOT:<br />
ssh vpk@clon00<br />
cmroot claswolf hist_claswolf<br />
<br />
* to kill DAQ:<br />
wolfram_exit<br />
<br />
<br />
'''Expert Information:'''<br />
<br />
[[ADC Pedestals Measurement Procedure]]<br />
<br />
[[Alarm Browser]]<br />
<br />
[[Alarm Server]]<br />
<br />
[[Data Monitoring]]<br />
<br />
[[dbrouter]]<br />
<br />
[[Epics Server]]<br />
<br />
[[ET System]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[info_server]]<br />
<br />
[[Logbook]]<br />
<br />
[[msql database]]<br />
<br />
[[Process Management]]<br />
<br />
[[Recsis]]<br />
<br />
[[sgutil]]<br />
<br />
[[Stadis]]<br />
<br />
[[CMON]] CLAS Online Data Monitoring<br />
<br />
[[Runlog]] programs</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CAEN_V560&diff=4844CAEN V5602010-06-24T17:46:31Z<p>129.57.76.146: </p>
<hr />
<div>Manual [https://clonwiki.jlab.org/wiki/clondocs/man/VME/CAEN_V560.pdf (pdf)]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CAEN_V560&diff=4843CAEN V5602010-06-24T17:46:05Z<p>129.57.76.146: </p>
<hr />
<div>Manual [https://clonwiki.jlab.org/wiki/clondocs/man/VME/v560.pdf (pdf)]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=4842CLON Index2010-06-24T17:45:47Z<p>129.57.76.146: </p>
<hr />
<div>[[Apache]]<br />
<br />
[[automounts]]<br />
<br />
[[Bertan MWPC]] High Voltage Power Supplies<br />
<br />
[[Bootp]]<br />
<br />
[[Cacti]]<br />
<br />
[[CAEN A464]] caenet board (installed in sy527 mainframes)<br />
<br />
[[CAEN SY1527 Mainframe]]<br />
<br />
[[CAEN SY527 Mainframe]] and modules<br />
<br />
[[CAEN V1190]] TDC board (128 ch 100 ps)<br />
<br />
[[CAEN V1290]] TDC board (32 ch 25 ps)<br />
<br />
[[CAEN V1495]] General Purpose VME Board<br />
<br />
[[CAEN V288]]<br />
<br />
[[CAEN V560]] scaler board<br />
<br />
[[CAEN V775]] TDC Board<br />
<br />
[[CAEN V895]] 16 ch. Leading Edge Discriminator with individual thresholds<br />
<br />
[[Capfast]]<br />
<br />
[[Cisco Switches]]<br />
<br />
[[Clasweb]]<br />
<br />
[[Clasxt]]<br />
<br />
[[Clon00]]<br />
<br />
[[Clon01]]<br />
<br />
[[Clon02]]<br />
<br />
[[Clon03]]<br />
<br />
[[Clon04]]<br />
<br />
[[Clon05]]<br />
<br />
[[Clon06]]<br />
<br />
[[Clon10]]<br />
<br />
[[Clon20]]<br />
<br />
[[Clondaq1]]<br />
<br />
[[Clondaq2]]<br />
<br />
[[Clondb1]]<br />
<br />
[[Clondb2]]<br />
<br />
[[Clonfs]] Main RAID System<br />
<br />
[[Clonfs1]]<br />
<br />
[[Clonfs2]]<br />
<br />
[[Clonmon]]<br />
<br />
[[Clonmon0]]<br />
<br />
[[Clonmon1]]<br />
<br />
[[Clonmon2]]<br />
<br />
[[Clonpc1]]<br />
<br />
[[Clonpc2]]<br />
<br />
[[Clonpc3]]<br />
<br />
[[Clonpc5]]<br />
<br />
[[Clonpc6]]<br />
<br />
[[Clonpc8]]<br />
<br />
[[Clonweb]]<br />
<br />
[[Clonwiki]]<br />
<br />
[[clonhp]]<br />
<br />
[[clonhp2]]<br />
<br />
[[Coda]]<br />
<br />
[[Compcontrol CC121]]<br />
<br />
[[CycladesTS1000]]<br />
<br />
[[DATEL DVME-628]]<br />
<br />
[[DNS server]]<br />
<br />
[[Electronics Documentation]]<br />
<br />
[[EtherLite32]]<br />
<br />
[[EPICS Base Installation]]<br />
<br />
[[EPICS: Generation of IOC with different options and customization for HallB]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: vxWorks IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Timeline Histories]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[Fiber Channel Switches]]<br />
<br />
[[FieldPoint]]<br />
<br />
[[Flash ADC Studies]]<br />
<br />
[[Foundry BigIron 15000 Switch]]<br />
<br />
[[Foundry Switches]]<br />
<br />
[[Helicity Signals from MCC]]<br />
<br />
[[HYTEC VSD2992]]<br />
<br />
[[JAVA installation]]<br />
<br />
[[JLAB Discriminators]]<br />
<br />
[[JLAB FLEXIO]]<br />
<br />
[[JLAB LF]] VME Latch FIFO Board<br />
<br />
[[JLAB LD]] VME Latch Driver Board<br />
<br />
[[JLAB Level2 Majority]] Logic Unit<br />
<br />
[[JLAB MLU]] VME Memory Lookup Unit (MLU)<br />
<br />
[[JLAB OR]] VME Programmable “OR” Module<br />
<br />
[[JLAB TS2]] VXI D-size Trigger Supervisor Module<br />
<br />
[[JLAB TI]] CODA Trigger Interface Cards<br />
<br />
[[JLAB PCI TI]] PCI Trigger Interface Card<br />
<br />
[[JLAB VME TI]] VME Trigger Interface Module<br />
<br />
[[Joerger VSC16]]<br />
<br />
[[KineticSystems 2917]]<br />
<br />
[[Labeling Machines]]<br />
<br />
[[Linux Installation Procedure]]<br />
<br />
[[Linux Customization on CLON Cluster]]<br />
<br />
[[Lnf cluster]]<br />
<br />
[[Mac OS X Installation Procedure]]<br />
<br />
[[Motorola MVME5500]]<br />
<br />
[[MRTG]]<br />
<br />
[[mSQL]]<br />
<br />
[[MySQL Installation]]<br />
<br />
[[MySQL Usage]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Net-SNMP]]<br />
<br />
[[NFS]]<br />
<br />
[[NIS server]]<br />
<br />
[[Nrpe]]<br />
<br />
[[Ntp]]<br />
<br />
[[OMS VME44]] by Oregon Micro Systems<br />
<br />
[[OMS VS4]] by Oregon Micro Systems<br />
<br />
[[OpenSSL]]<br />
<br />
[[PERL]]<br />
<br />
[[Procmail]]<br />
<br />
[[PrPMC]]<br />
<br />
[[raidold]]<br />
<br />
[[Routing]]<br />
<br />
[[Rrdtool]]<br />
<br />
[[SBS VIPC616]]<br />
<br />
[[Serial Connections from Computer Ports]]<br />
<br />
[[Sfs61]]<br />
<br />
[[Slow Controls Time History]]<br />
<br />
[[SmartSockets]]<br />
<br />
[[SNMP]]<br />
<br />
[[Software Documentation]]<br />
<br />
[[Solaris Installation Procedure]]<br />
<br />
[[Solaris Customization on CLON Cluster]]<br />
<br />
[[Solaris Patches]]<br />
<br />
[[SSH]]<br />
<br />
[[Struck SIS3801]]<br />
<br />
[[Sudo]]<br />
<br />
[[SUN Microsystems]]<br />
<br />
[[SYSTRAN VMESC5]]<br />
<br />
[[Tcl/Tk]]<br />
<br />
[[Tftp]]<br />
<br />
[[Troubleshooting printing]]<br />
<br />
[[UNIX Automount on CLON Cluster]]<br />
<br />
[[UPS (Uninterruptible Power Supplies)]]<br />
<br />
[[UPS CHB1]]<br />
<br />
[[UPS CHB2]]<br />
<br />
[[UPS Troubleshooting]]<br />
<br />
[[VI editor]]<br />
<br />
[[VMIC VMIVME-3122]]<br />
<br />
[[VMIC VMIVME-2120]]<br />
<br />
[[VMIC VMIVME-1129]]<br />
<br />
[[VMIC VMIVME-2232]]<br />
<br />
[[VMIC VMIVME-6015]]<br />
<br />
[[VMIC VMIVME-6016]]<br />
<br />
[[VNC]]<br />
<br />
[[WIENER]]<br />
<br />
[[Wiki]]<br />
<br />
[[Wiring]]<br />
<br />
[[X server]]<br />
<br />
[[Xycom DIO XVME-240]]<br />
<br />
[[Xycom XVME-564]]<br />
<br />
[[Xycom XVME-560]]<br />
<br />
[[ZFS]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=4841CLON Index2010-06-24T17:45:37Z<p>129.57.76.146: </p>
<hr />
<div>[[Apache]]<br />
<br />
[[automounts]]<br />
<br />
[[Bertan MWPC]] High Voltage Power Supplies<br />
<br />
[[Bootp]]<br />
<br />
[[Cacti]]<br />
<br />
[[CAEN A464]] caenet board (installed in sy527 mainframes)<br />
<br />
[[CAEN SY1527 Mainframe]]<br />
<br />
[[CAEN SY527 Mainframe]] and modules<br />
<br />
[[CAEN V1190]] TDC board (128 ch 100 ps)<br />
<br />
[[CAEN V1290]] TDC board (32 ch 25 ps)<br />
<br />
[[CAEN V1495]] General Purpose VME Board<br />
<br />
[[CAEN V288]]<br />
<br />
[[CAEN V569]] scaler board<br />
<br />
[[CAEN V775]] TDC Board<br />
<br />
[[CAEN V895]] 16 ch. Leading Edge Discriminator with individual thresholds<br />
<br />
[[Capfast]]<br />
<br />
[[Cisco Switches]]<br />
<br />
[[Clasweb]]<br />
<br />
[[Clasxt]]<br />
<br />
[[Clon00]]<br />
<br />
[[Clon01]]<br />
<br />
[[Clon02]]<br />
<br />
[[Clon03]]<br />
<br />
[[Clon04]]<br />
<br />
[[Clon05]]<br />
<br />
[[Clon06]]<br />
<br />
[[Clon10]]<br />
<br />
[[Clon20]]<br />
<br />
[[Clondaq1]]<br />
<br />
[[Clondaq2]]<br />
<br />
[[Clondb1]]<br />
<br />
[[Clondb2]]<br />
<br />
[[Clonfs]] Main RAID System<br />
<br />
[[Clonfs1]]<br />
<br />
[[Clonfs2]]<br />
<br />
[[Clonmon]]<br />
<br />
[[Clonmon0]]<br />
<br />
[[Clonmon1]]<br />
<br />
[[Clonmon2]]<br />
<br />
[[Clonpc1]]<br />
<br />
[[Clonpc2]]<br />
<br />
[[Clonpc3]]<br />
<br />
[[Clonpc5]]<br />
<br />
[[Clonpc6]]<br />
<br />
[[Clonpc8]]<br />
<br />
[[Clonweb]]<br />
<br />
[[Clonwiki]]<br />
<br />
[[clonhp]]<br />
<br />
[[clonhp2]]<br />
<br />
[[Coda]]<br />
<br />
[[Compcontrol CC121]]<br />
<br />
[[CycladesTS1000]]<br />
<br />
[[DATEL DVME-628]]<br />
<br />
[[DNS server]]<br />
<br />
[[Electronics Documentation]]<br />
<br />
[[EtherLite32]]<br />
<br />
[[EPICS Base Installation]]<br />
<br />
[[EPICS: Generation of IOC with different options and customization for HallB]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: vxWorks IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Timeline Histories]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[Fiber Channel Switches]]<br />
<br />
[[FieldPoint]]<br />
<br />
[[Flash ADC Studies]]<br />
<br />
[[Foundry BigIron 15000 Switch]]<br />
<br />
[[Foundry Switches]]<br />
<br />
[[Helicity Signals from MCC]]<br />
<br />
[[HYTEC VSD2992]]<br />
<br />
[[JAVA installation]]<br />
<br />
[[JLAB Discriminators]]<br />
<br />
[[JLAB FLEXIO]]<br />
<br />
[[JLAB LF]] VME Latch FIFO Board<br />
<br />
[[JLAB LD]] VME Latch Driver Board<br />
<br />
[[JLAB Level2 Majority]] Logic Unit<br />
<br />
[[JLAB MLU]] VME Memory Lookup Unit (MLU)<br />
<br />
[[JLAB OR]] VME Programmable “OR” Module<br />
<br />
[[JLAB TS2]] VXI D-size Trigger Supervisor Module<br />
<br />
[[JLAB TI]] CODA Trigger Interface Cards<br />
<br />
[[JLAB PCI TI]] PCI Trigger Interface Card<br />
<br />
[[JLAB VME TI]] VME Trigger Interface Module<br />
<br />
[[Joerger VSC16]]<br />
<br />
[[KineticSystems 2917]]<br />
<br />
[[Labeling Machines]]<br />
<br />
[[Linux Installation Procedure]]<br />
<br />
[[Linux Customization on CLON Cluster]]<br />
<br />
[[Lnf cluster]]<br />
<br />
[[Mac OS X Installation Procedure]]<br />
<br />
[[Motorola MVME5500]]<br />
<br />
[[MRTG]]<br />
<br />
[[mSQL]]<br />
<br />
[[MySQL Installation]]<br />
<br />
[[MySQL Usage]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Net-SNMP]]<br />
<br />
[[NFS]]<br />
<br />
[[NIS server]]<br />
<br />
[[Nrpe]]<br />
<br />
[[Ntp]]<br />
<br />
[[OMS VME44]] by Oregon Micro Systems<br />
<br />
[[OMS VS4]] by Oregon Micro Systems<br />
<br />
[[OpenSSL]]<br />
<br />
[[PERL]]<br />
<br />
[[Procmail]]<br />
<br />
[[PrPMC]]<br />
<br />
[[raidold]]<br />
<br />
[[Routing]]<br />
<br />
[[Rrdtool]]<br />
<br />
[[SBS VIPC616]]<br />
<br />
[[Serial Connections from Computer Ports]]<br />
<br />
[[Sfs61]]<br />
<br />
[[Slow Controls Time History]]<br />
<br />
[[SmartSockets]]<br />
<br />
[[SNMP]]<br />
<br />
[[Software Documentation]]<br />
<br />
[[Solaris Installation Procedure]]<br />
<br />
[[Solaris Customization on CLON Cluster]]<br />
<br />
[[Solaris Patches]]<br />
<br />
[[SSH]]<br />
<br />
[[Struck SIS3801]]<br />
<br />
[[Sudo]]<br />
<br />
[[SUN Microsystems]]<br />
<br />
[[SYSTRAN VMESC5]]<br />
<br />
[[Tcl/Tk]]<br />
<br />
[[Tftp]]<br />
<br />
[[Troubleshooting printing]]<br />
<br />
[[UNIX Automount on CLON Cluster]]<br />
<br />
[[UPS (Uninterruptible Power Supplies)]]<br />
<br />
[[UPS CHB1]]<br />
<br />
[[UPS CHB2]]<br />
<br />
[[UPS Troubleshooting]]<br />
<br />
[[VI editor]]<br />
<br />
[[VMIC VMIVME-3122]]<br />
<br />
[[VMIC VMIVME-2120]]<br />
<br />
[[VMIC VMIVME-1129]]<br />
<br />
[[VMIC VMIVME-2232]]<br />
<br />
[[VMIC VMIVME-6015]]<br />
<br />
[[VMIC VMIVME-6016]]<br />
<br />
[[VNC]]<br />
<br />
[[WIENER]]<br />
<br />
[[Wiki]]<br />
<br />
[[Wiring]]<br />
<br />
[[X server]]<br />
<br />
[[Xycom DIO XVME-240]]<br />
<br />
[[Xycom XVME-564]]<br />
<br />
[[Xycom XVME-560]]<br />
<br />
[[ZFS]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_June_16,_2010&diff=4840CLON meeting June 16, 20102010-06-17T14:49:05Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, June 16 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current run status<br />
<br />
2. CLAS12 DAQ development as part of CLAS12 workshop</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=June_16,_2010_online_meeting_minutes&diff=4839June 16, 2010 online meeting minutes2010-06-17T14:47:14Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Ben Raydo, David Abbott, Eugene Pasyuk, Chris Cuevas<br />
<br />
1. Run status<br />
<br />
We still experience 'end run failure' occationally, known TS2 problem still to be fixed, then will check the problem if it stays<br />
<br />
2. CLAS12 project was discussed<br />
<br />
* JLAB discriminators: 5 boards in testing by several groups; geographical addressing may be useful to have, VME64X must be used for that, Ben will look at that option<br />
<br />
* DC electronics: management support, ADBTDC board to be designed; if money are available, Ben can start to work on DC project this fall<br />
<br />
* GTP board: have not enough lines, we need GTP to read from 16 slots<br />
<br />
* Heavy Photon Search experiment: use new TIs only, because we need block readout to get 50kHz<br />
<br />
* CTP board: we need 8GBit connection from FADC boards to have 8bit ADC value from every channel every 16ns; Hall B will pay for 2 new CTP prototypes wich advanced FPGA to speedup connection</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=4838CLON Group Meetings2010-06-17T14:43:25Z<p>129.57.76.146: /* 2010 */</p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
== 2007 ==<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
== 2008 ==<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]<br />
<br />
== 2009 ==<br />
<br />
[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 2, 2009]] >>>>> [[September 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 23, 2009]] >>>>> [[September 23, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 30, 2009]] >>>>> [[September 30, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting October 14, 2009]] >>>>> [[October 14, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting November 11, 2009]] >>>>> [[November 11, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 2, 2009]] >>>>> [[December 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 16, 2009]] >>>>> [[December 16, 2009 online meeting minutes]]<br />
<br />
== 2010 ==<br />
<br />
[[CLON meeting January 13, 2010]] >>>>> [[January 13, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting January 27, 2010]] >>>>> [[January 27, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 10, 2010]] >>>>> [[February 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 24, 2010]] >>>>> [[February 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 10, 2010]] >>>>> [[March 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 17, 2010]] >>>>> [[March 17, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 24, 2010]] >>>>> [[March 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 7, 2010]] >>>>> [[April 7, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 21, 2010]] >>>>> [[April 21, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 5, 2010]] >>>>> [[May 5, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 12, 2010]] >>>>> [[May 12, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 26, 2010]] >>>>> [[May 26, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting June 9, 2010]] >>>>> [[June 9, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting June 16, 2010]] >>>>> [[June 16, 2010 online meeting minutes]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=June_9,_2010_online_meeting_minutes&diff=4830June 9, 2010 online meeting minutes2010-06-10T13:27:05Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Nerses Gevorgyan<br />
<br />
* level2 reset works; sometimes level2 alarm induced by low voltage failure or other problems, maybe need to modify message on alarm browser<br />
<br />
* dc hv: caenet send command delay was adjusted, will start from 20ms and increse 50ms every time we are trying again; tested in test setup, works fine, will be tested in the hall later<br />
<br />
* raid disk: upper unit power supplies (both) went down again, as result lower unit does not communicate now, Paul Letta will check it<br />
<br />
* clondaq2: yellow light, need service; ask Paul about server processor commands and update solaris wiki page; 10Gig link was lost, Bryan Hess touched connectors and replaced optic cable, works now<br />
<br />
* print problems were obsetved on some clons, need check<br />
<br />
* l2_status_dead probably must be removed from cronjob, since we have alarm from the dccntrl crate's process; error (DISPLAY not set for cron jobs,tcl's wish seems want it) in log file must be addressed in any case<br />
<br />
Other issues:<br />
<br />
* linear fanouts: philips about $1000, will buy, including for SCU<br />
* have 5 spare CAMAC power supplies now (3 repaired, 2 found)<br />
* Nerses is working on harp scan issues on intel solaris, will be fixed soon; histo solid filling in 'medm' works on sparc solaris only, will be addressed as well</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_June_9,_2010&diff=4829CLON meeting June 9, 20102010-06-10T13:18:32Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, June 9 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current g9frost run status<br />
* level2<br />
* dc high voltage<br />
* raid<br />
.....</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=4828CLON Group Meetings2010-06-10T13:17:16Z<p>129.57.76.146: /* 2010 */</p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
== 2007 ==<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
== 2008 ==<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]<br />
<br />
== 2009 ==<br />
<br />
[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 2, 2009]] >>>>> [[September 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 23, 2009]] >>>>> [[September 23, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 30, 2009]] >>>>> [[September 30, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting October 14, 2009]] >>>>> [[October 14, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting November 11, 2009]] >>>>> [[November 11, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 2, 2009]] >>>>> [[December 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 16, 2009]] >>>>> [[December 16, 2009 online meeting minutes]]<br />
<br />
== 2010 ==<br />
<br />
[[CLON meeting January 13, 2010]] >>>>> [[January 13, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting January 27, 2010]] >>>>> [[January 27, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 10, 2010]] >>>>> [[February 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 24, 2010]] >>>>> [[February 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 10, 2010]] >>>>> [[March 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 17, 2010]] >>>>> [[March 17, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 24, 2010]] >>>>> [[March 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 7, 2010]] >>>>> [[April 7, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 21, 2010]] >>>>> [[April 21, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 5, 2010]] >>>>> [[May 5, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 12, 2010]] >>>>> [[May 12, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 26, 2010]] >>>>> [[May 26, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting June 9, 2010]] >>>>> [[June 9, 2010 online meeting minutes]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Clondaq2&diff=4827Clondaq22010-06-07T14:23:08Z<p>129.57.76.146: </p>
<hr />
<div>Clondaq2 is X4200 server running Solaris, s/n: 0626AM2523, f/n: F46985. It is second DAQ server serving mostly to run Event Recorder and handle SILO traffic.<br />
<br />
Network ports:<br />
<br />
clondaq2 - e1000g0<br />
clondaq2-daq1 - ixgb0 (10GBit; was e1000g1 while 1GBit)<br />
clondaq2-daq2 - e1000g2<br />
<br />
After Solaris installation:<br />
<br />
1. Create ''/ssa'' directory and make following links there:<br />
<br />
cd /ssa<br />
ln -s /mnt/raid0 active<br />
ln -s /mnt/raid1 epmty<br />
ln -s /mnt/raid2 postsilo1<br />
ln -s /mnt/raid3 postsilo2<br />
<br />
2. Create two files in ''/ssa'' directory:<br />
<br />
''/ssa/ENVIRONMENT'' contains:<br />
<br />
set PARTITIONS = " raid0 raid1 raid2 raid3 "<br />
set LOGFILE = "/ssa/logfile"<br />
set CLON_LOG = "/usr/clas/logs"<br />
<br />
''/ssa/STUB.TARGET'' contains:<br />
<br />
/mss/clas/dvcs2/data<br />
<br />
(or whatever run period you are in)<br />
<br />
3. Make ''/raid/stage_in'' link:<br />
<br />
cd /<br />
ln -s /ssa/active raid<br />
<br />
4. Make ''/mss'' link:<br />
<br />
cd /<br />
ln -s /w/mss mss<br />
<br />
5. Adjust [[Sudo]] config file.<br />
<br />
6. Make sure [[ZFS]] RAID partitions are mounted.<br />
<br />
7. [[Routing]] must be adjusted to make sure input and output traffics are taking different routes.<br />
<br />
8. [[automounts]] settings must be modified for clondaq2: new file ''/etc/auto_stage'' must be created with following contents:<br />
<br />
stage0 -rsize=1048576,wsize=1048576 sfs61:/export/stage<br />
stage1 -rsize=1048576,wsize=1048576 sfs56:/export/stage<br />
stage2 -rsize=1048576,wsize=1048576 sfs59:/export/stage<br />
+auto.w.ep<br />
<br />
and in file ''/etc/auto_master'' instead of ''/w auto.w.ep'' must use ''/w /etc/auto_stage''.<br />
<br />
'''NOTE''': June 6, 2010 10GBit connection was lost (clondaq2-daq1), Bryan Hess checked it and found that unplugging/plugging helps; he replaced cable just in case, well watch it (I think it is not the first time ...)</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4824Sgutil2010-06-02T18:12:02Z<p>129.57.76.146: </p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
Example can be found [https://clonwiki.jlab.org/wiki/clondocs/Docs/sgutil_fig7_8.pdf here].<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/sgutil_fig9.pdf adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains participated wire numbers, the slope and the shift between superlayers (latest value represents the phi angle of the track). If thresholds are reasonably high (4 and 8 for superlayer and region respectively) then the list will be short, for our example (fig.2) only one region-based segment will be reported as following: axial wire numbers are 66,66,0,0,65,65; stereo wire numbers are 70,70,0,69,0,69; slope 33; phi 17 (slope and phi are reported as an corresponding table indexes).<br />
<br />
It takes an average few hundreds of microseconds on regular PC to process segment finding for one event with the efficiency of 96-98%. To get remaining few percent thresholds must be lowered which leads to the significant increase of both the execution time and the number of segment candidates. As result following road finding procedure must deal with the huge number of combinations which increases execution time even more. In general drift chamber inefficiency was the biggest challenge for the speed of the presented approach. It was used successfully in online reconstruction where some inefficiency is allowed, however in the level 3 (software) trigger it was running in tagging mode only.<br />
<br />
There is a plan to use described approach in upcoming CLAS12 Trigger System as FPGA-based implementation, where in can be executed much fasted. We hope to address 'dead' wired issue and develop fast and efficient component of the Level 1 (hardware) trigger.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4823Sgutil2010-06-02T18:11:31Z<p>129.57.76.146: </p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
Example can be found [https://clonwiki.jlab.org/wiki/clondocs/Docs/sgutil_fig8_9.pdf here].<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/sgutil_fig9.pdf adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains participated wire numbers, the slope and the shift between superlayers (latest value represents the phi angle of the track). If thresholds are reasonably high (4 and 8 for superlayer and region respectively) then the list will be short, for our example (fig.2) only one region-based segment will be reported as following: axial wire numbers are 66,66,0,0,65,65; stereo wire numbers are 70,70,0,69,0,69; slope 33; phi 17 (slope and phi are reported as an corresponding table indexes).<br />
<br />
It takes an average few hundreds of microseconds on regular PC to process segment finding for one event with the efficiency of 96-98%. To get remaining few percent thresholds must be lowered which leads to the significant increase of both the execution time and the number of segment candidates. As result following road finding procedure must deal with the huge number of combinations which increases execution time even more. In general drift chamber inefficiency was the biggest challenge for the speed of the presented approach. It was used successfully in online reconstruction where some inefficiency is allowed, however in the level 3 (software) trigger it was running in tagging mode only.<br />
<br />
There is a plan to use described approach in upcoming CLAS12 Trigger System as FPGA-based implementation, where in can be executed much fasted. We hope to address 'dead' wired issue and develop fast and efficient component of the Level 1 (hardware) trigger.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4822Sgutil2010-06-02T18:08:59Z<p>129.57.76.146: </p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/sgutil_fig9.pdf adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains participated wire numbers, the slope and the shift between superlayers (latest value represents the phi angle of the track). If thresholds are reasonably high (4 and 8 for superlayer and region respectively) then the list will be short, for our example (fig.2) only one region-based segment will be reported as following: axial wire numbers are 66,66,0,0,65,65; stereo wire numbers are 70,70,0,69,0,69; slope 33; phi 17 (slope and phi are reported as an corresponding table indexes).<br />
<br />
It takes an average few hundreds of microseconds on regular PC to process segment finding for one event with the efficiency of 96-98%. To get remaining few percent thresholds must be lowered which leads to the significant increase of both the execution time and the number of segment candidates. As result following road finding procedure must deal with the huge number of combinations which increases execution time even more. In general drift chamber inefficiency was the biggest challenge for the speed of the presented approach. It was used successfully in online reconstruction where some inefficiency is allowed, however in the level 3 (software) trigger it was running in tagging mode only.<br />
<br />
There is a plan to use described approach in upcoming CLAS12 Trigger System as FPGA-based implementation, where in can be executed much fasted. We hope to address 'dead' wired issue and develop fast and efficient component of the Level 1 (hardware) trigger.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4821Sgutil2010-06-02T15:24:54Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains participated wire numbers, the slope and the shift between superlayers (latest value represents the phi angle of the track). If thresholds are reasonably high (4 and 8 for superlayer and region respectively) then the list will be short, for our example (fig.2) only one region-based segment will be reported as following: axial wire numbers are 66,66,0,0,65,65; stereo wire numbers are 70,70,0,69,0,69; slope 33; phi 17 (slope and phi are reported as an corresponding table indexes).<br />
<br />
It takes an average few hundreds of microseconds on regular PC to process segment finding for one event with the efficiency of 96-98%. To get remaining few percent thresholds must be lowered which leads to the significant increase of both the execution time and the number of segment candidates. As result following road finding procedure must deal with the huge number of combinations which increases execution time even more. In general drift chamber inefficiency was the biggest challenge for the speed of the presented approach. It was used successfully in online reconstruction where some inefficiency is allowed, however in the level 3 (software) trigger it was running in tagging mode only.<br />
<br />
There is a plan to use described approach in upcoming CLAS12 Trigger System as FPGA-based implementation, where in can be executed much fasted. We hope to address 'dead' wired issue and develop fast and efficient component of the Level 1 (hardware) trigger.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4820Sgutil2010-06-02T15:09:58Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains participated wire numbers, the slope and the shift between superlayers (latest value represents the phi angle of the track). If thresholds are reasonably high (4 and 8 for superlayer and region respectively) then the list will be short, for our example (fig.2) only one region-based segment will be reported as following: axial wire numbers are 66,66,0,0,65,65; stereo wire numbers are 70,70,0,69,0,69; slope 33; phi 17 (slope and phi are reported as an corresponding table indexes).</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4819Sgutil2010-06-02T15:03:29Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. Another threshold has been applied to the region-based segments, usually minimum 8 hits were required. Again, threshold was lowered later because of 'dead' wires to burst segment search efficiency. As soon as threshold is decreased, the length of the segment list grows significantly, and execution time come with it.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of region-based segments is created. Every segment in the list contains origin wire number, slope and shift between superlayers (latest value represents the phi angle of the track).</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4818Sgutil2010-06-02T14:51:19Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers stored in 192-dim arrays. Those arrays will be used on the following steps (fig.2). Only segments with the number of hits above threshold are kept. As it was found threshold equal to 4 is the best from both segment search efficiency and execution time prospectives. However because of significant number of the 'dead' wires in some areas that threshold must be set to 3, which increases significantly the number of segment candidates and execution time per event. One way to address the issue would be to convert 'dead' wires into 'hot' wires assigning hits to them permanently, but it is not the part of existing procedure. <br />
<br />
On the second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced. It should be mentioned <br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4817Sgutil2010-06-02T14:40:49Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. Track segments search is the first stage of the pattern recognition process (second stage is road finding) which is part of level 3 (software) trigger, as well as online event reconstruction software.<br />
<br />
The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Segments in 2 superlayers can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removal is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers for the set of shift patterns representing different track segment angles from +30 to -30 degrees approximately. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6, which means layers 4,5 and 6 were shifted one step to the left. After every shift, 192-bit words were summed using binary numbers adding procedure as it was suggested by Pavel Degtyarenko (fig.3). Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using 3x8 lookup tables those numbers are converted into integers to be used on the following step (fig.2).<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=Sgutil&diff=4812Sgutil2010-06-01T15:59:16Z<p>129.57.76.146: /* NIM paper draft */</p>
<hr />
<div>'''SGLIB/SGUTIL''' package contains Dave Haddle's noise reduction software with segment finding extensions. It resides in ''$CODA/src/codatt/sgutil.c'' and is called from ''$CLON/src/cmon/prlib/sglib.c''.<br />
<br />
'''SGLIB''' contains following functions:<br />
<br />
* ''sginit()'' - must be called once at initialization stage; creates differencial shift table and fills lookup tables<br />
<br />
* ''sgtrigger()'' - works for specified sector; return 0 if sector does not have required track information, otherwise returns the number of superlayers with segments; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sgremovenoise()'' - works for specified sector; rewrites all DC banks removing single hits; calls function ''RemoveNoise()'' from '''SGUTIL'''<br />
<br />
* ''sglib()'' - find segments for one sector; three options can be specified: noise removing only, segment finding only, noise removing and then segment finding; calls functions ''RemoveNoise()'', ''SegmentSearch128()'' and ''SegmentSearch192()'' from '''SGUTIL'''<br />
<br />
* ''sgprint()'' - print results for one sector<br />
<br />
* sgroad()'' - fill road finding structures, SWAPING region 1<br />
<br />
'''SGUTIL''' contains following functions:<br />
<br />
* ''BinaryPrint32()'', ''PrintWord192()'', ''CopyWord192()'', ''ANDWord192()'', ''ORWord192()'', ''XORWord192()'', ''CheckBitWord192()'', ''SetBitWord192()'', ''ClearWord192()'', ''NegateWord192()'', ''BleedRightWord192()'', ''BleedLeftWord192()'' - functions for 192-bit words operations<br />
<br />
* ''RightShiftWord192()'', ''LeftShiftWord192()'', ''RIGHTSHIFT()'', ''RightShiftWord192_00()'', ''RightShiftWord192_01()'', ''RightShiftWord192_02()'', ''RightShiftWord192_03()'', ''LEFTSHIFT()'', ''LeftShiftWord192_00()'', ''LeftShiftWord192_01()'', ''LeftShiftWord192_02()'', ''LeftShiftWord192_03()'' - macroses for 192-bit words operations<br />
<br />
* ''RemoveNoise()'' - works for one superlayer, removes single hits; it is very much the same as original Dave's program, with some optimization; it returns 0 if nothing left after single hits removing, or 1 otherwise<br />
<br />
* ''SuperLayerSum()'' - used by ''RemoveNoise()'' only; does fast summing of the 6 192-bit words following algorithm suggested by Pavel Degtiarenko; output is the 192-bit word where every bit contains result of the summing of the corresponding 6-bit vertical column<br />
<br />
'''ALGORITHMS DESCRIPTION'''<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, [https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
''SegmentSearch192'' searches for segments in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number<br />
of hits. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.<br />
<br />
''SegmentSearch192'' calls 4 macros:<br />
<br />
'''TWOSLPROCESS(192)''':<br />
<br />
* input: superlayer data in a form of 6 192-bit words (layers); ''dshift'' table<br />
* action: loop over ''NSHIFT'' shifts, shifting layers in according to ''dshift'' table, binary summing 6 layers, store results in 3 192-bit words, convert bit sums to integer sums using '3 layers 4 bits' lookup table method<br />
* output: ''char tmp1[NSHIFT][192]'' (superlayer1) and ''char tmp2[NSHIFT][192]'' (superlayer2) - the number of hits for every wire and every shift<br />
<br />
'''REGIONPROCESS(192)''':<br />
<br />
* input: tmp1[NSHIFT][192] and tmp2[NSHIFT][192] from previous macro<br />
* action: loop over ''NSHIFT'' shifts, nested loop over superlayer-to-superlayer shift<br />
* output: list of region-based segments: <br />
<br />
'''PEAKSEARCH(192)''':<br />
<br />
'''SEGMENTLIST(192)''':<br />
<br />
== NIM paper draft ==<br />
<br />
<br />
Described approach was used to search for the track segments. The segment finding process can be explained using data sample shown on fig.1. Drift chamber consists of 3 regions, each contains axial and stereo superlayers. Track segment inside the region can be considered as straight line, so program is looking for the segments with the same slope in both superlayers. Such segments can be spaced few wires from each other due to the phi angle of the track, which creates another degree of freedom.<br />
<br />
Noise removing is usually running first to cleanup data as much as possible. Red color hits on fig.1 will be removed at that point.<br />
<br />
Segment search is conducted in 3 steps. On the first step shift-and-sum operation is performed separately for axial and stereo superlayers. In our example (as it shown on fig.2) shift pattern was (0,0,1,1,1) for layers 2 through 6. <br />
<br />
Results are stored in 3 192-bit words, where vertical 3-bit columns contains the number of hits in binary format. Using lookup tables those numbers are converted into integers to be used on following step.<br />
<br />
<br />
<br />
192-bit words were summed using binary numbers adding procedure. As it was suggested by Pavel Degtyarenko, <br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr000.gif simple adder] was implemented, and following<br />
[https://clonwiki.jlab.org/wiki/clondocs/Docs/faddr-4b.gif adding procedure] was used to get a sum of 6 192-bit words representing 6 layers of the Drift Chamber superlayer. This method was used in ''SuperLayerSum/RemoveNoise'' procedure to found areas with segments, and in the first stage of ''SegmentSearch192'' procedure.<br />
<br />
<br />
On second step one of the superlayers is shifted against another one, search is conducted for the region-based segments, and list of segment candidates is produced.<br />
<br />
On the third step segment list is processed to select the segment with the maximum number of hits, and final list of segments is created.</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=May_26,_2010_online_meeting_minutes&diff=4811May 26, 2010 online meeting minutes2010-06-01T15:42:48Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Stepan Stepanyan<br />
<br />
1. Current run status: several problems were observed:<br />
<br />
* all level2 reset lines were connected, automatic reset system under testing<br />
* tage3 cannot boot sometimes, 'vital data ...' message is showing up, power recycle helps; may need to re-flash, or replace the CPU board<br />
* dc10 had readout problem, FASTBUS termination cards were replaced, it works now, will try to check removed card to confirm the problem cause and fix them<br />
* tage was power recycled once because did to boot remotely, works fine now<br />
* end run failed still happens, need more information, will ask shift personal to record messages from clastrig2<br />
* run_log_begin sometimes segment faults, as result txt file does not creates and database is not updating, will put debug messages and watch <br />
<br />
2. Primex2<br />
<br />
* while no decision yet on the next run, we'll start preparations for primex2, because it may take a while to restore its DAQ; list of missing electronics was created, we'll assemble missing boards and repair broken ones; daq will be configured (CLAS version with coda format), and we'll try to run DAQ in parallel with current run</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=May_26,_2010_online_meeting_minutes&diff=4810May 26, 2010 online meeting minutes2010-06-01T15:42:31Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Stepan Stepanyan<br />
<br />
1. Current run status: several problems were observed:<br />
<br />
* all level2 reset lines were connected, automatic reset system under testing<br />
* tage3 cannot boot sometimes, 'vital data ...' message is showing up, power recycle helps; may need to re-flash, or replace the CPU board<br />
* dc10 had readout problem, FASTBUS termination cards were replaced, it works now, will try to check removed card to confirm the problem cause and fix them<br />
* tage was power recycled once because did to boot remotely, works fine now<br />
* end run failed still happens, need more information, will ask shift personal to record messages from clastrig2<br />
* run_log_begin sometimes segment faults, as result txt file does not creates and database is not updating, will put debug messages and watch <br />
<br />
2. Others<br />
<br />
* while no decision yet on the next run, we'll start preparations for primex2, because it may take a while to restore its DAQ; list of missing electronics was created, we'll assemble missing boards and repair broken ones; daq will be configured (CLAS version with coda format), and we'll try to run DAQ in parallel with current run</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_May_26,_2010&diff=4809CLON meeting May 26, 20102010-06-01T15:40:15Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, May 26 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current g9frost run status<br />
* level2<br />
* dc10, tage3 problems<br />
<br />
2. PRIMEX2 preparations</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=May_26,_2010_online_meeting_minutes&diff=4808May 26, 2010 online meeting minutes2010-06-01T15:37:26Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Stepan Stepanyan<br />
<br />
1. Current run status: several problems were observed:<br />
<br />
* tage3 cannot boot sometimes, 'vital data ...' message is showing up, power recycle helps; may need to re-flash, or replace the CPU board<br />
* tage was power recycled once because did to boot remotely, works fine now<br />
* end run failed still happens, need more information, will ask shift personal to record messages from clastrig2<br />
* run_log_begin sometimes segment faults, as result txt file does not creates and database is not updating, will put debug messages and watch <br />
<br />
2. Others<br />
<br />
* while no decision yet on the next run, we'll start preparations for primex2, because it may take a while to restore its DAQ; list of missing electronics was created, we'll assemble missing boards and repair broken ones; daq will be configured (CLAS version with coda format), and we'll try to run DAQ in parallel with current run</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=4807CLON Group Meetings2010-06-01T14:34:34Z<p>129.57.76.146: /* 2010 */</p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
== 2007 ==<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
== 2008 ==<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]<br />
<br />
== 2009 ==<br />
<br />
[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 2, 2009]] >>>>> [[September 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 23, 2009]] >>>>> [[September 23, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 30, 2009]] >>>>> [[September 30, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting October 14, 2009]] >>>>> [[October 14, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting November 11, 2009]] >>>>> [[November 11, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 2, 2009]] >>>>> [[December 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 16, 2009]] >>>>> [[December 16, 2009 online meeting minutes]]<br />
<br />
== 2010 ==<br />
<br />
[[CLON meeting January 13, 2010]] >>>>> [[January 13, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting January 27, 2010]] >>>>> [[January 27, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 10, 2010]] >>>>> [[February 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 24, 2010]] >>>>> [[February 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 10, 2010]] >>>>> [[March 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 17, 2010]] >>>>> [[March 17, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 24, 2010]] >>>>> [[March 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 7, 2010]] >>>>> [[April 7, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 21, 2010]] >>>>> [[April 21, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 5, 2010]] >>>>> [[May 5, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 12, 2010]] >>>>> [[May 12, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 26, 2010]] >>>>> [[May 26, 2010 online meeting minutes]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=March_24,_2010_online_meeting_minutes&diff=4779March 24, 2010 online meeting minutes2010-05-05T16:05:31Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Mac Mestayer, Eugene Pasyuk<br />
<br />
1. g9frost run:<br />
<br />
* EB1 problem still there - working on it<br />
<br />
* FAST clear was going from generator 4us fixed, now it goes directly from TS2,<br />
must check again with 1881 manual; check 1877 fast clear as well<br />
<br />
* normalization trigger to be tested<br />
<br />
* MOR in trigger to be studied<br />
<br />
* NOTE: deadtime dominated by rejected events<br />
<br />
* TOF threshold<br />
<br />
* EPICS Ok, DB Ok<br />
<br />
* online recsis need to be fixed<br />
<br />
* trigger stydies at 2pm today<br />
<br />
<br />
2. inventory<br />
<br />
Features:<br />
<br />
* every item must be labeled<br />
<br />
* new fields (status: new options like purchased, inspected visualy etc)<br />
<br />
* 'NOW' IN PURCHASE INFO<br />
<br />
* can we use logbook for dc group ???</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=April_7,_2010_online_meeting_minutes&diff=4778April 7, 2010 online meeting minutes2010-05-05T16:00:54Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Vitaly Baturin<br />
<br />
1. g9frost run status<br />
<br />
- online recsis works: cvs co, fixed, ci, co - works; need it in svn/scon (jerry/dennis)<br />
<br />
- caget run_number fixed; will be good to fix event rate/data rate etc<br />
<br />
- daq problems under debugging: EB waiting, clastrig2 end run -> polar crash,<br />
clastrig2 go (200 events, probably related); will debug in test setup and then<br />
in CLAS during downtime<br />
<br />
- TOF mainframe #4 gives alarm, EPICS ON/OFF does not work, roc_reboot ioc (classc12) complains<br />
about mainframe #4; temporary taken out from boot script; need to fix and restore startrup script<br />
<br />
<br />
2. CLAS12 electronics<br />
<br />
- new electronics table was created with updated amount and prices, management is working<br />
to address money increase<br />
<br />
- 5 JLAB discriminators almost ready, will be tested<br />
<br />
- HV, crates to be ordered with Hall D</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=May_5,_2010_online_meeting_minutes&diff=4777May 5, 2010 online meeting minutes2010-05-05T15:56:10Z<p>129.57.76.146: </p>
<hr />
<div>present: Sergey Boyarinov, Sergey Pozdnyakov, Eugene Pasyuk, Stepan Stepanyan, Vitaly Baturin<br />
<br />
1. current run:<br />
<br />
Sergey P. found some camac bira supplies, they will be delivered to counting house<br />
and tested; sergey fixed one supply himself (fuse holder replaced)<br />
<br />
paging gui works fine; old pagers to be replaced even if not in use<br />
<br />
<br />
2. new level2 will be installed tomorrow (parcialy first 6 closest, to be<br />
tested, maybe in parallel with old system); log file will be written<br />
<br />
<br />
OTHERS:<br />
<br />
midelsim ordered<br />
<br />
fadc needed for PCAL tests, sometime in fall (November); fadc (about $160000)<br />
will be payed from CLAS capital, the rest from CLAS12; single pixel trigger<br />
must be programmed; may need discr and tdcs<br />
<br />
vitaly is moving; buy new clon20 ??? old clon20 will be desconnected and<br />
stored; ethernet will go from old youri place to the new vitaly's</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_May_5,_2010&diff=4776CLON meeting May 5, 20102010-05-05T15:54:28Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, May 5 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current g9frost run status<br />
<br />
2. New level2 reset system</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_April_21,_2010&diff=4775CLON meeting April 21, 20102010-05-05T15:53:47Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, April 21 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current g9frost run status<br />
<br />
2. SLAC experiment preparations</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_Group_Meetings&diff=4774CLON Group Meetings2010-05-05T15:53:35Z<p>129.57.76.146: /* 2010 */</p>
<hr />
<div>[[CLON meeting December 13, 2006]] >>>>> [[December 13, 2006 online meeting minutes]]<br />
<br />
== 2007 ==<br />
<br />
[[CLON meeting September 5, 2007]] >>>>> [[September 5, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 12, 2007]] >>>>> [[September 12, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 19, 2007]] >>>>> [[September 19, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting September 26, 2007]] >>>>> [[September 26, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 3, 2007]] >>>>> [[October 3, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 10, 2007]] >>>>> [[October 10, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 17, 2007]] >>>>> [[October 17, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 24, 2007]] >>>>> [[October 24, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting October 31, 2007]] >>>>> [[October 31, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 7, 2007]] >>>>> [[November 7, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 14, 2007]] >>>>> [[November 14, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting November 28, 2007]] >>>>> [[November 28, 2007 online meeting minutes]]<br />
<br />
[[CLON meeting December 12, 2007]] >>>>> [[December 12, 2007 online meeting minutes]]<br />
<br />
== 2008 ==<br />
<br />
[[CLON meeting January 16, 2008]] >>>>> [[January 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 23, 2008]] >>>>> [[January 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting January 30, 2008]] >>>>> [[January 30, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting February 13, 2008]] >>>>> [[February 13, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 5, 2008]] >>>>> [[March 5, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 12, 2008]] >>>>> [[March 12, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting March 26, 2008]] >>>>> [[March 26, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 16, 2008]] >>>>> [[April 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting April 23, 2008]] >>>>> [[April 23, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting May 21, 2008]] >>>>> [[May 21, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 4, 2008]] >>>>> [[June 4, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting June 18, 2008]] >>>>> [[June 18, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 2, 2008]] >>>>> [[July 2, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting July 16, 2008]] >>>>> [[July 16, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 10, 2008]] >>>>> [[September 10, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 17, 2008]] >>>>> [[September 17, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting September 24, 2008]] >>>>> [[September 24, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 1, 2008]] >>>>> [[October 1, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting October 15, 2008]] >>>>> [[October 15, 2008 online meeting minutes]]<br />
<br />
[[CLON meeting November 12, 2008]] >>>>> [[November 12, 2008 online meeting minutes]]<br />
<br />
== 2009 ==<br />
<br />
[[CLON meeting January 21, 2009]] >>>>> [[January 21, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting January 28, 2009]] >>>>> [[January 28, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 4, 2009]] >>>>> [[February 4, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 18, 2009]] >>>>> [[February 18, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting February 25, 2009]] >>>>> [[February 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting March 25, 2009]] >>>>> [[March 25, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 8, 2009]] >>>>> [[April 8, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting April 22, 2009]] >>>>> [[April 22, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 6, 2009]] >>>>> [[May 6, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting May 20, 2009]] >>>>> [[May 20, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 3, 2009]] >>>>> [[June 3, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 10, 2009]] >>>>> [[June 10, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting June 17, 2009]] >>>>> [[June 17, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting July 1, 2009]] >>>>> [[July 1, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 2, 2009]] >>>>> [[September 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 23, 2009]] >>>>> [[September 23, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting September 30, 2009]] >>>>> [[September 30, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting October 14, 2009]] >>>>> [[October 14, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting November 11, 2009]] >>>>> [[November 11, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 2, 2009]] >>>>> [[December 2, 2009 online meeting minutes]]<br />
<br />
[[CLON meeting December 16, 2009]] >>>>> [[December 16, 2009 online meeting minutes]]<br />
<br />
== 2010 ==<br />
<br />
[[CLON meeting January 13, 2010]] >>>>> [[January 13, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting January 27, 2010]] >>>>> [[January 27, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 10, 2010]] >>>>> [[February 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting February 24, 2010]] >>>>> [[February 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 10, 2010]] >>>>> [[March 10, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 17, 2010]] >>>>> [[March 17, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting March 24, 2010]] >>>>> [[March 24, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 7, 2010]] >>>>> [[April 7, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting April 21, 2010]] >>>>> [[April 21, 2010 online meeting minutes]]<br />
<br />
[[CLON meeting May 5, 2010]] >>>>> [[May 5, 2010 online meeting minutes]]</div>129.57.76.146https://clonwiki0.jlab.org/wiki/index.php?title=CLON_meeting_April_7,_2010&diff=4773CLON meeting April 7, 20102010-05-05T15:51:36Z<p>129.57.76.146: </p>
<hr />
<div>Clas On-line Meeting, Wednesday, April 7 at 10am in Room A110<br />
------------------------------------------------------------------<br />
<br />
1. Current g9frost run status<br />
<br />
2. CLAS12 electronics updated list</div>129.57.76.146