September 25, 2013 online meeting minutes - Revision history

129.57.81.115 at 15:05, 25 September 2013

2013-09-25T15:05:11Z

← Older revision		Revision as of 11:05, 25 September 2013
Line 7:		Line 7:
	Our next goal to maasure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.		Our next goal to maasure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.

	Busy condition have to be issued by GTP (on fifo full for example).		Busy condition have to be issued by GTP (on fifo full for example). Initially GTP readout will be done using tcpServer, will work for readout OR diagnostics, not both at the same time. In a future it can be Linux core.

129.57.81.115 at 15:03, 25 September 2013

2013-09-25T15:03:24Z

← Older revision		Revision as of 11:03, 25 September 2013
Line 6:		Line 6:

	Our next goal to maasure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.		Our next goal to maasure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.

			Busy condition have to be issued by GTP (on fifo full for example).

129.57.81.115 at 14:35, 25 September 2013

2013-09-25T14:35:16Z

← Older revision		Revision as of 10:35, 25 September 2013
Line 5:		Line 5:
	Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.		Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.

	Our next goal to ~~make sure~~ trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.		Our next goal to maasure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.

129.57.81.115 at 14:34, 25 September 2013

2013-09-25T14:34:47Z

← Older revision		Revision as of 10:34, 25 September 2013
Line 2:		Line 2:

	1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible. Resulting table updated every 128 ns. Timing window for hits persistence is set to 2 us, trigger clock in GTP is 8 ns now and can be less frequent.		1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible. Resulting table updated every 128 ns. Timing window for hits persistence is set to 2 us, trigger clock in GTP is 8 ns now and can be less frequent.
	Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.
	Our next goal to make sure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.		Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.

			Our next goal to make sure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.

129.57.81.115 at 14:29, 25 September 2013

2013-09-25T14:29:57Z

← Older revision		Revision as of 10:29, 25 September 2013
Line 3:		Line 3:
	1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible. Resulting table updated every 128 ns. Timing window for hits persistence is set to 2 us, trigger clock in GTP is 8 ns now and can be less frequent.		1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible. Resulting table updated every 128 ns. Timing window for hits persistence is set to 2 us, trigger clock in GTP is 8 ns now and can be less frequent.
	Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.		Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.
			Our next goal to make sure trigger efficiency comparing trigger data with offline pattern recognition and running from scintillator telescope. Later we'll try to improve resolution of segments reported by tracking trigger.

129.57.81.115 at 14:25, 25 September 2013

2013-09-25T14:25:51Z

← Older revision		Revision as of 10:25, 25 September 2013
Line 1:		Line 1:
	present: Sergey Boyarinov, Ben Raydo, Mac Mestayer		present: Sergey Boyarinov, Ben Raydo, Mac Mestayer

	1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible.		1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible. Resulting table updated every 128 ns. Timing window for hits persistence is set to 2 us, trigger clock in GTP is 8 ns now and can be less frequent.
			Readout from GTP to be implemented, so trigger data recorded along with coda_roc data. GTP data will have trigger timestamp for doublecheck. The way to readout data from GTP to be decided.

129.57.81.115: Created page with "present: Sergey Boyarinov, Ben Raydo, Mac Mestayer 1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup whic..."

2013-09-25T14:08:39Z

Created page with "present: Sergey Boyarinov, Ben Raydo, Mac Mestayer 1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup whic..."

New page

present: Sergey Boyarinov, Ben Raydo, Mac Mestayer

1. Ben released first revision of segment finder implemented in GTP board used as CTP. It is installed in DCRB test setup which is currently connected to the CLAS12 region1 drift chamber located in clean room 124 (EEL bldg). Segment finder searches for 12 hit segments and reports results in a form of 2-dim array (x-starting wire number, y-delta between ending wire number and starting wire number). There is no sorting of segments found, so several similar segments reported into 2-dim table. One improvement would be to sort those segments selecting one 'the best' if possible.