April 23, 2008 online meeting minutes - Revision history

129.57.121.200 at 16:26, 23 April 2008

2008-04-23T16:26:30Z

← Older revision		Revision as of 12:26, 23 April 2008
Line 7:		Line 7:
	Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.		Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.

	2. We discussed our experience with [[New CLAS Level1 Trigger System]] implementation.		2. We discussed our experience with [[New CLAS Level1 Trigger System]] implementation. David will create generic library for v1495 which can be used by other Halls personal. We need to create an documentation and provide basic training (if Ben have a time !) so people can use those boards for at least simple applications. Appropriate machine and lincensed software from Altera maybe necessary as well, although free versions (including simulation tools) can be used on Windows machines.

129.57.121.200 at 16:21, 23 April 2008

2008-04-23T16:21:40Z

← Older revision		Revision as of 12:21, 23 April 2008
Line 7:		Line 7:
	Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.		Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.

	2. We discussed our experience with [New CLAS Level1 Trigger System] implementation.		2. We discussed our experience with [[New CLAS Level1 Trigger System]] implementation.

129.57.121.200 at 16:20, 23 April 2008

2008-04-23T16:20:51Z

← Older revision		Revision as of 12:20, 23 April 2008
Line 7:		Line 7:
	Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.		Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.

	2. We discussed an experience with ~~new v1495-based trigger system development and implementation, it can be found [~~[~~here]~~].		2. We discussed our experience with [New CLAS Level1 Trigger System] implementation.

129.57.121.200 at 16:18, 23 April 2008

2008-04-23T16:18:26Z

← Older revision		Revision as of 12:18, 23 April 2008
Line 5:		Line 5:
	New Scintillator Hodoscope ADCs, TDCs and discriminators were connected and programmed, still need to finisg scalers wiring. Data need to be analysed to make sure everything connected properly. Discriminators control is in 'dimanv', Sergey P. will send to Stepan short instruction howto use it.		New Scintillator Hodoscope ADCs, TDCs and discriminators were connected and programmed, still need to finisg scalers wiring. Data need to be analysed to make sure everything connected properly. Discriminators control is in 'dimanv', Sergey P. will send to Stepan short instruction howto use it.

			Inventory database was presented on last Monday meeting. More improvements needed for front end, in particular the date of last change must be implemented, and search for the range of those dates will be useful. It is probably a good idea to make separate maintenance history table instead of ascii records.

	2.		2. We discussed an experience with new v1495-based trigger system development and implementation, it can be found [[here]].

129.57.121.200 at 16:13, 23 April 2008

2008-04-23T16:13:57Z

← Older revision		Revision as of 12:13, 23 April 2008
Line 3:		Line 3:
	1. G12 run finally have new v1495-based level1 trigger commissioned, it is running at 8kHz with 12% deadtime and 35MB/s data rate. Level2 is used as well. DAQ looks stable. EPICS histograms for new trigger system were reportedly implemented by Nerses, we'll activate them shortly.		1. G12 run finally have new v1495-based level1 trigger commissioned, it is running at 8kHz with 12% deadtime and 35MB/s data rate. Level2 is used as well. DAQ looks stable. EPICS histograms for new trigger system were reportedly implemented by Nerses, we'll activate them shortly.

	New Scintillator Hodoscope ADCs, TDCs and discriminators were connected and programmed, still need to finisg scalers wiring. Data need to be analysed to make sure everything connected properly.		New Scintillator Hodoscope ADCs, TDCs and discriminators were connected and programmed, still need to finisg scalers wiring. Data need to be analysed to make sure everything connected properly. Discriminators control is in 'dimanv', Sergey P. will send to Stepan short instruction howto use it.


	2.		2.

129.57.121.200 at 16:12, 23 April 2008

2008-04-23T16:12:39Z

New page

present: Sergey Boyarinov, Sergey Pozdnyakov, David Abbott

1. G12 run finally have new v1495-based level1 trigger commissioned, it is running at 8kHz with 12% deadtime and 35MB/s data rate. Level2 is used as well. DAQ looks stable. EPICS histograms for new trigger system were reportedly implemented by Nerses, we'll activate them shortly.

New Scintillator Hodoscope ADCs, TDCs and discriminators were connected and programmed, still need to finisg scalers wiring. Data need to be analysed to make sure everything connected properly.

2.