Difference between revisions of "Minutes-3-6-2014"
| Line 29: | Line 29: | ||
- Most of the discussions were about the cathode scan. All the details are in the E-log entries 142 and 143. The main issues are: | - Most of the discussions were about the cathode scan. All the details are in the E-log entries 142 and 143. The main issues are: | ||
| − | # | + | ##Why there are valid points in the middle of the cathode where there is no copper. |
| − | # | + | ##How to explain the extra gap (by ~250 microns) between the strips exactly in the middle of the cathode. |
Revision as of 17:13, 6 March 2014
February 27, 2014 FDC meeting
Agenda
- Installation status
- Engineering (Bill)
- Electronics problematic channels (Chris, Nick)
- Mini-DAQ status FDC E-log (Beni)
- Other
Minutes
Participants: Elton, Fernando, Dave, Chris, Bill, Beni, and Lubomir. Given the urgency of the FDC testing before the insertion, the agenda was somewhat different.
Testing and Installation
- Beni: The tests done with the fADC125 firmware with 10 and 100 samples (hard coded by Cody) showed the same problem: after several thousand good events, there's a corrupted one (with a wrong length) and after that all are corrupted and there's no way to recover. As for the option to return back to the Gerard's code that was certainly working, the only way to do it is by manually re-programing again all the fADCs. Fernando: Cody, Bryan and Hai are working on this problem and they understand the urgency. Fernando hopes that very soon we will have a working code.
- Lubomir: as of today we started testing the cathode channels with a scope (plan B). It will take about a day per package, so certainly by Tuesday we will be ready. With a scope you can't see all the problems (like frequency of the cosmics, or low amplitude noise) but one can identify the symptoms caused by a bad conductive tape: no signal at all or very small amplitude. So, at least we can identify and fix these. If by the next week we have the fADC working we can test all the channels in one night. In any case we decided to plan inserting the FDC at the end of the next week. If we have the fADCs we will immediately test all the channels after the insertion and by March 17 we should know if there are significant problems that will require to pull the FDC back on the platform.
- There were some discussions initiated by Beni and Fernando, about what will be the consequences if the FDC installation is delayed say by a month. The CDC installation will be delayed, but then the other detectors are not ready for installation. After the meeting Elton discussed this with Tim: we are behind the schedule and more delays will make it even more difficult to do everything that is left in shorter time with the same people.
Electronics
- By the beginning of the next week we will have a list with problematic connectors and Chris will start fixing them. The difficult part will be to fix the 3M connectors (at the electronics side), but at least Chris can open them and try to identify the issue. If we are sure that it is the 3M connector he can fix them later.
Engineering
- Most of the discussions were about the cathode scan. All the details are in the E-log entries 142 and 143. The main issues are:
- Why there are valid points in the middle of the cathode where there is no copper.
- How to explain the extra gap (by ~250 microns) between the strips exactly in the middle of the cathode.
