| ID |
Date |
Author |
Subject |
|
166
|
Wed Mar 2 11:59:48 2016 |
PJCS | First data with two streams merged from one FEE64 |
The Fail bit is used to indicate The Timing Vernier word.
I'll post a seperate Elog entry to explain the format.
>
> My GREAT data analyser program reports that the 'fail' bit is set ?
>
> $ ./a.exe v R1_0 | more
> *** GREAT format 3.2.0 analyser - TD - May 2014
> verbose
> *** SYNC100 timestamp: block: 1 ptr: 7 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C088000A0
> *** SYNC100 timestamp: block: 1 ptr: 9 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C088400A0
> *** SYNC100 timestamp: block: 1 ptr: 11 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C088800A0
> *** SYNC100 timestamp: block: 1 ptr: 13 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C088C00A0
> *** SYNC100 timestamp: block: 1 ptr: 15 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C089000A0
> *** SYNC100 timestamp: block: 1 ptr: 17 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C089400A0
> *** SYNC100 timestamp: block: 1 ptr: 19 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C089800A0
> *** SYNC100 timestamp: block: 1 ptr: 21 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C089C00A0
> *** SYNC100 timestamp: block: 1 ptr: 23 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08A000A0
> *** SYNC100 timestamp: block: 1 ptr: 25 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08A400A0
> *** SYNC100 timestamp: block: 1 ptr: 27 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08A800A0
> *** SYNC100 timestamp: block: 1 ptr: 29 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08AC00A0
> *** SYNC100 timestamp: block: 1 ptr: 31 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08B000A0
> *** SYNC100 timestamp: block: 1 ptr: 33 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08B400A0
> *** SYNC100 timestamp: block: 1 ptr: 35 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08B800A0
> *** SYNC100 timestamp: block: 1 ptr: 37 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08BC00A0
> *** SYNC100 timestamp: block: 1 ptr: 39 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08C000A0
> *** SYNC100 timestamp: block: 1 ptr: 41 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08C400A0
> *** SYNC100 timestamp: block: 1 ptr: 43 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08C800A0
> *** SYNC100 timestamp: block: 1 ptr: 45 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08CC00A0
> *** SYNC100 timestamp: block: 1 ptr: 47 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08D000A0
> *** SYNC100 timestamp: block: 1 ptr: 49 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08D400A0
> *** SYNC100 timestamp: block: 1 ptr: 51 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08D800A0
> *** SYNC100 timestamp: block: 1 ptr: 53 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08DC00A0
> *** SYNC100 timestamp: block: 1 ptr: 55 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08E000A0
> *** SYNC100 timestamp: block: 1 ptr: 57 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08E400A0
> *** SYNC100 timestamp: block: 1 ptr: 59 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08E800A0
> *** SYNC100 timestamp: block: 1 ptr: 61 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08EC00A0
> *** SYNC100 timestamp: block: 1 ptr: 63 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08F000A0
> *** SYNC100 timestamp: block: 1 ptr: 65 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08F400A0
> *** SYNC100 timestamp: block: 1 ptr: 67 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08F800A0
> *** SYNC100 timestamp: block: 1 ptr: 69 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C08FC00A0
> *** SYNC100 timestamp: block: 1 ptr: 71 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C090000A0
> *** SYNC100 timestamp: block: 1 ptr: 73 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C090400A0
> *** SYNC100 timestamp: block: 1 ptr: 75 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C090800A0
> *** SYNC100 timestamp: block: 1 ptr: 77 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C090C00A0
> *** SYNC100 timestamp: block: 1 ptr: 79 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C091000A0
> *** SYNC100 timestamp: block: 1 ptr: 81 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C091400A0
> *** SYNC100 timestamp: block: 1 ptr: 83 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C091800A0
> *** SYNC100 timestamp: block: 1 ptr: 85 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C091C00A0
> *** SYNC100 timestamp: block: 1 ptr: 87 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C092000A0
> *** SYNC100 timestamp: block: 1 ptr: 89 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C092400A0
> *** SYNC100 timestamp: block: 1 ptr: 91 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C092800A0
> *** SYNC100 timestamp: block: 1 ptr: 93 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C092C00A0
> *** SYNC100 timestamp: block: 1 ptr: 95 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C093000A0
> *** SYNC100 timestamp: block: 1 ptr: 97 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C093400A0
> *** SYNC100 timestamp: block: 1 ptr: 99 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C093800A0
> *** SYNC100 timestamp: block: 1 ptr: 101 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C093C00A0
> *** SYNC100 timestamp: block: 1 ptr: 103 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C094000A0
> *** SYNC100 timestamp: block: 1 ptr: 105 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C094400A0
> *** SYNC100 timestamp: block: 1 ptr: 107 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C094800A0
> *** SYNC100 timestamp: block: 1 ptr: 109 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C094C00A0
> *** SYNC100 timestamp: block: 1 ptr: 111 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C095000A0
> *** SYNC100 timestamp: block: 1 ptr: 113 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C095400A0
> *** SYNC100 timestamp: block: 1 ptr: 115 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C095800A0
> *** SYNC100 timestamp: block: 1 ptr: 117 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C095C00A0
> *** SYNC100 timestamp: block: 1 ptr: 119 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C096000A0
> *** SYNC100 timestamp: block: 1 ptr: 121 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C096400A0
> *** SYNC100 timestamp: block: 1 ptr: 123 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C096800A0
> *** SYNC100 timestamp: block: 1 ptr: 125 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C096C00A0
> *** SYNC100 timestamp: block: 1 ptr: 127 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C097000A0
> *** SYNC100 timestamp: block: 1 ptr: 129 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C097400A0
> *** SYNC100 timestamp: block: 1 ptr: 131 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C097800A0
> *** SYNC100 timestamp: block: 1 ptr: 133 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C097C00A0
> *** SYNC100 timestamp: block: 1 ptr: 135 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C098000A0
> *** SYNC100 timestamp: block: 1 ptr: 137 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C098400A0
> *** SYNC100 timestamp: block: 1 ptr: 139 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C098800A0
> *** SYNC100 timestamp: block: 1 ptr: 141 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C098C00A0
> *** SYNC100 timestamp: block: 1 ptr: 143 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C099000A0
> *** SYNC100 timestamp: block: 1 ptr: 145 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C099400A0
> *** SYNC100 timestamp: block: 1 ptr: 147 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C099800A0
> *** SYNC100 timestamp: block: 1 ptr: 149 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C099C00A0
> *** SYNC100 timestamp: block: 1 ptr: 151 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09A000A0
> *** SYNC100 timestamp: block: 1 ptr: 153 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09A400A0
> *** SYNC100 timestamp: block: 1 ptr: 155 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09A800A0
> *** SYNC100 timestamp: block: 1 ptr: 157 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09AC00A0
> *** SYNC100 timestamp: block: 1 ptr: 159 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09B000A0
> *** SYNC100 timestamp: block: 1 ptr: 161 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09B400A0
> *** SYNC100 timestamp: block: 1 ptr: 163 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09B800A0
> *** SYNC100 timestamp: block: 1 ptr: 165 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09BC00A0
> *** SYNC100 timestamp: block: 1 ptr: 167 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09C000A0
> *** SYNC100 timestamp: block: 1 ptr: 169 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09C400A0
> *** SYNC100 timestamp: block: 1 ptr: 171 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09C800A0
> *** SYNC100 timestamp: block: 1 ptr: 173 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09CC00A0
> *** SYNC100 timestamp: block: 1 ptr: 175 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09D000A0
> *** SYNC100 timestamp: block: 1 ptr: 177 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09D400A0
> *** SYNC100 timestamp: block: 1 ptr: 179 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09D800A0
> *** SYNC100 timestamp: block: 1 ptr: 181 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09DC00A0
> *** SYNC100 timestamp: block: 1 ptr: 183 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09E000A0
> *** SYNC100 timestamp: block: 1 ptr: 185 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09E400A0
> *** SYNC100 timestamp: block: 1 ptr: 187 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09E800A0
> *** SYNC100 timestamp: block: 1 ptr: 189 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09EC00A0
> *** SYNC100 timestamp: block: 1 ptr: 191 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09F000A0
> *** SYNC100 timestamp: block: 1 ptr: 193 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09F400A0
> *** SYNC100 timestamp: block: 1 ptr: 195 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09F800A0
> *** SYNC100 timestamp: block: 1 ptr: 197 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C09FC00A0
> *** SYNC100 timestamp: block: 1 ptr: 199 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C0A0000A0
> *** SYNC100 timestamp: block: 1 ptr: 201 data: 0x824000C0 module: 2 information type: 4 information
> field: 0x000000C0 ts: 0x000C0A0400A0
> *** ADC data: block: 1 ptr: 203 data: 0xD08FFFFF module: 2 fail: 0 range: 1 id: 143
> channel: 15 adc: 65535 ts: 0x000C0A0411AE
>
> *** SYNC100 timestamp: block: 3 ptr: 1071 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C7000A0
> *** ERROR: fail bit set: block: 3 ptr: 1073 data:E09F0730
> *** ADC data: block: 3 ptr: 1073 data: 0xE09F0730 module: 2 fail: 1 range: 0 id: 159
> channel: 31 adc: 1840 ts: 0x000D0C71DC7E
> *** SYNC100 timestamp: block: 3 ptr: 1075 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C7400A0
> *** SYNC100 timestamp: block: 3 ptr: 1077 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C7800A0
> *** SYNC100 timestamp: block: 3 ptr: 1079 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C7C00A0
> *** SYNC100 timestamp: block: 3 ptr: 1081 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C8000A0
> *** ERROR: fail bit set: block: 3 ptr: 1083 data:E09F0678
> *** ADC data: block: 3 ptr: 1083 data: 0xE09F0678 module: 2 fail: 1 range: 0 id: 159
> channel: 31 adc: 1656 ts: 0x000D0C811EB8
> *** SYNC100 timestamp: block: 3 ptr: 1085 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C8400A0
> *** SYNC100 timestamp: block: 3 ptr: 1087 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C8800A0
> *** SYNC100 timestamp: block: 3 ptr: 1089 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C8C00A0
> *** SYNC100 timestamp: block: 3 ptr: 1091 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C9000A0
> *** ERROR: fail bit set: block: 3 ptr: 1093 data:E09F06BC
> *** ADC data: block: 3 ptr: 1093 data: 0xE09F06BC module: 2 fail: 1 range: 0 id: 159
> channel: 31 adc: 1724 ts: 0x000D0C9060F0
> *** SYNC100 timestamp: block: 3 ptr: 1095 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C9400A0
> *** SYNC100 timestamp: block: 3 ptr: 1097 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C9800A0
> *** SYNC100 timestamp: block: 3 ptr: 1099 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0C9C00A0
> *** ERROR: fail bit set: block: 3 ptr: 1101 data:E09F0703
> *** ADC data: block: 3 ptr: 1101 data: 0xE09F0703 module: 2 fail: 1 range: 0 id: 159
> channel: 31 adc: 1795 ts: 0x000D0C9FA328
> *** SYNC100 timestamp: block: 3 ptr: 1103 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0CA000A0
> *** SYNC100 timestamp: block: 3 ptr: 1105 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0CA400A0
> *** SYNC100 timestamp: block: 3 ptr: 1107 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0CA800A0
> *** SYNC100 timestamp: block: 3 ptr: 1109 data: 0x824000D0 module: 2 information type: 4 information
> field: 0x000000D0 ts: 0x000D0CAC00A0
> *** ERROR: fail bit set: block: 3 ptr: 1111 data:E09F0749
>
>
> blocks: 14
> ADC data format: 21180 ( 86.8 Hz)
> Other data format: 93060 ( 381.5 Hz)
> Sample trace data format: 0 ( 0.0 Hz)
> Undefined format: 0 ( 0.0 Hz)
> Other data format type: PAUSE: 0 ( 0.0 Hz)
> RESUME: 0 ( 0.0 Hz)
> SYNC100: 93060 ( 381.5 Hz)
> FEE64 disc: 0 ( 0.0 Hz)
> MBS info: 0 ( 0.0 Hz)
> Other info: 0 ( 0.0 Hz)
>
> ADC data range bit set: 1239 ( 5.1 Hz)
>
> Timewarps: ADC: 0 ( 0.0 Hz)
> PAUSE: 0 ( 0.0 Hz)
> RESUME: 0 ( 0.0 Hz)
> SYNC100: 0 ( 0.0 Hz)
> FEE64 disc: 0 ( 0.0 Hz)
> MBS info: 0 ( 0.0 Hz)
> Undefined: 0 ( 0.0 Hz)
> Sample trace: 0 ( 0.0 Hz)
>
> Timestamp elapsed time: 243.950 s
>
> *** Program elapsed time: 0.719s ( 19.478 blocks/s, 1.217 Mb/s) |
|
544
|
Wed Mar 29 13:38:38 2017 |
OH, DK, CG | First beam runs |
For BigRIPS run numbers, they are available online: http://bripscnt01.rarfadv.riken.jp/runsum/index.php
21:30 AIDA and BRIKEN are ready to go -- so we closed the door and asked the BigRIPS team to send the beam to
F11. It will take about 30 minutes as they want to recalibrate one of the Faraday cups.
22:09: Beam is coming to F11. AIDA sub-run R13_17 is running at 22:10 so nearly the same time.
BigRIPS run number 0140
BRIKEN file name 170329_2213_40Mg Run 0. It is started at 22:13. R13_18 for AIDA
See attachment 1 for biases.
23:12: We notice that BigRIPS began the run 0141 at 23:08
AIDA subrun R13_36 began about or near 23:07 or 23:08
BRIKEN run number 170329_2313_40Mg Run 1
All system-wide checks passed (excepting nnaida6 clock status which is a known issue)
Statistics rates look reasonable, except that the nnaida 16 23 24 are even higher than before when the beam
was off (~200k)
23:59 - AIDA crashed. Merger stopped. When attempting to stop the run, the following error is displayed:
STATE for nnaida1 returned with an error
error: SOAP http transport timed out after 20000 ms
NONE
error: SOAP http transport timed out after 20000 ms
while executing
"$transport $procVarName $url $req"
(procedure "::SOAP::invoke" line 18)
invoked from within
"::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetState"
("eval" body line 1)
invoked from within
"eval ::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetState $args"
(procedure "DataAcquisitionControlClient__GetState" line 1)
invoked from within
"DataAcquisitionControlClient__GetState"
We kill off the merge and tape server.
DAQ itself comes back after a reset. Attempting to open the tape service, however, yields an error
Cannot issue more Access Tokens
ClaimTapeServer returned:-
3 Capability table is full.
30.3.2017
0:56 When attempting to bring AIDA back up, eventually nnaida10 was not showing merger data before enabling the
ASIC readout data. On the run control, nnaida10 consistently showed that its data transfer was not enabled.
Attempting to reset etc., then eventually issuing Go would drop all the data transfers.
After a power cycle by the standard method, essentially the problem persists, except that it is nnaida 7 8 9 10
(the whole block) which shows the problem where we cannot get the enabled data transfer to stick. |
| Attachment 1: biases_firstbeam.png
|
|
|
276
|
Sun Jun 5 01:32:44 2016 |
TD, DK, GL, AE, PJW | First RIB implantation: Run 67 |
We restarted the merger (Stop, Setup & Configure, Go, Pause) and then we could restart the DAQ as normal. Rate is ~500 Hz. |
|
21
|
Wed Jan 14 15:29:01 2015 |
Patrick | Filtered switch mode PSU performance |
Trying the AIDA format power supply with the simple filters installed.
The detector is attached and HV of 200v@3.8uA
Using one channel from each FEE64 as a guide to compare performance. Using the Integrate analysis function Peak width.
With the bench power supply and the restored setup for the ASICs.
FEE64 #11:1.4.L:311, #12:2.8.L:183, #13:1.4.L:202, #14:1.4.L:342
Change to the filtered power supply
FEE64 #11:1.4.L:345, #12:2.8.L:414, #13:1.4.L:311, #14:1.4.L:476
Add Braid between the LEMO00 connectors on the two adaptor boards using "croc" clips.
FEE64 #11:1.4.L:172, #12:2.8.L:141, #13:1.4.L:106, #14:1.4.L:161
Change the shaping time of all the ASICs from 0.5uS to 5uS
FEE64 #11:1.4.L:128, #12:2.8.L:127, #13:1.4.L:119, #14:1.4.L:199
I think this means the AIDA power supply with the simple filters is equivalent or better than the bench supply.
Good news I think.....
It needs a more extensive test ( more channels ? ) |
|
81
|
Wed Apr 29 11:34:09 2015 |
Patrick Coleman-Smith | Fast Trigger timings against Pulser Input and LEC/MEC Fast Comparator threshold setting |
I have tried the latest version ( 26 ) of the FEE64 code and carried out some measurements of the Fast Trigger delay from the Pulser signal ( not the Pulser Trigger out ) and observed the following.
The pulser gives a centroid of 28217 in the histogram.
| Threshold setting |
Delay observed at MACB Fast Trigger output (nS) |
| 0x40 |
no Trigger |
| 0x38 |
no Trigger |
| 0x30 |
no Trigger |
| 0x28 |
1200 to 1800 |
| 0x20 |
690 to 860 |
| 0x18 |
505 to 600 |
| 0x10 |
320 to 385 |
| 0x8 |
210 to 270 |
This seems to me to be sensible as the discriminator is only a very simple comparator.
The OR64 ( 0xE ) signal works as True Fast NIM Logic. The OR16s ( 0xC ) logic works as inverse Fast NIM.
The OR64 is derived from the individual masked discriminator outputs. By default the Mask is not set.
|
|
79
|
Wed Apr 29 10:01:27 2015 |
Patrick Coleman-Smith | Fast Trigger output fault in FEE64 FPGA logic |
The Fast Trigger output of the FEE64 is formed from the OR of the four OR16 signals ( one from each of the ASICs.
The logic levels of the OR16 signals are active low in the FPGA and so if the are OR'd together then the output is inactive if any one of the ASICs is inactive.
This is a problem when the Fast Trigger is being used by other DAQ systems.
A new FPGA program 0x1b4FE01A ( version 26 ) is being compiled.
The Fast Trigger output will provide the logic AND of the four OR16 signals which should give the correct signal. This setting is selected by "Setup".
The other settings available using the Trigger register are shown below. Note that OR64 is the logic OR of the masked outputs of the ASIC individual Discriminator outputs.
when 0 =>
trigger_hit <= ASIC1_data_ready ;
when 1 =>
trigger_hit <= ASIC1_rdo_range and ASIC1_data_ready ;
when 2 =>
trigger_hit <= ASIC2_rdo_range and ASIC2_data_ready ;
when 3 =>
trigger_hit <= led_trigger(0) ;
when 4 =>
trigger_hit <= led_raw(0) ;
when 5 =>
trigger_hit <= chan_reset(0) ;
when 6 =>
trigger_hit <= force_capture_sync ;
when 7 =>
trigger_hit <= force_capture ;
when 8 =>
trigger_hit <= ASIC1_OR_16 ;
when 9 =>
trigger_hit <= ASIC2_OR_16 ;
when 10 =>
trigger_hit <= ASIC3_OR_16 ;
when 11 =>
trigger_hit <= ASIC4_OR_16 ;
when 12 =>
trigger_hit <= ASIC4_OR_16 and ASIC3_OR_16 and ASIC2_OR_16 and ASIC1_OR_16;
when 13 =>
trigger_hit <= led_trigger(1) ;
when 14 =>
trigger_hit <= OR64 ;
when 15 =>
trigger_hit <= ASIC4_OR_16 or ASIC3_OR_16 or ASIC2_OR_16 or ASIC1_OR_16; |
|
589
|
Mon May 22 10:29:11 2017 |
TD | FEE64 system console to Raspberry pi /dev/ttyUSB mapping |
ttyUSB0 => last host=nnaida24, => last addr=10.1.2.24, ; #panics => 0 ; Not Finished
ttyUSB1 => last host=nnaida23, => last addr=10.1.2.23, ; #panics => 0 ; Not Finished
ttyUSB10 => last host=nnaida18, => last addr=10.1.1.18, ; #panics => 0 ; Not Finished
ttyUSB11 => last host=nnaida17, => last addr=10.1.1.17, ; #panics => 0 ; Not Finished
ttyUSB12 => last host=nnaida4, => last addr=10.1.2.4, ; #panics => 0 ; Not Finished
ttyUSB13 => last host=nnaida3, => last addr=10.1.2.3, ; #panics => 0 ; Not Finished
ttyUSB14 => last host=nnaida12, => last addr=10.1.2.12, ; #panics => 0 ; Not Finished
ttyUSB15 => last host=nnaida11, => last addr=10.1.2.11, ; #panics => 0 ; Not Finished
ttyUSB16 => last host=nnaida20, => last addr=10.1.2.20, ; #panics => 0 ; Not Finished
ttyUSB17 => last host=nnaida19, => last addr=10.1.2.19, ; #panics => 0 ; Not Finished
ttyUSB18 => last host=nnaida6, => last addr=10.1.1.6, ; #panics => 0 ; Not Finished
ttyUSB19 => last host=nnaida5, => last addr=10.1.1.5, ; #panics => 0 ; Not Finished
ttyUSB2 => last host=nnaida16, => last addr=10.1.2.16, ; #panics => 0 ; Not Finished
ttyUSB20 => last host=nnaida14, => last addr=10.1.1.14, ; #panics => 0 ; Not Finished
ttyUSB21 => last host=nnaida13, => last addr=10.1.1.13, ; #panics => 0 ; Not Finished
ttyUSB22 => last host=nnaida22, => last addr=10.1.1.22, ; #panics => 0 ; Not Finished
ttyUSB23 => last host=nnaida21, => last addr=10.1.1.21, ; #panics => 0 ; Not Finished
ttyUSB3 => last host=nnaida15, => last addr=10.1.2.15, ; #panics => 0 ; Not Finished
ttyUSB4 => last host=nnaida8, => last addr=10.1.2.8, ; #panics => 0 ; Not Finished
ttyUSB5 => last host=nnaida7, => last addr=10.1.2.7, ; #panics => 0 ; Not Finished
ttyUSB6 => last host=nnaida2, => last addr=10.1.1.2, ; #panics => 0 ; Not Finished
ttyUSB7 => last host=nnaida1, => last addr=10.1.1.1, ; #panics => 0 ; Not Finished
ttyUSB8 => last host=nnaida10, => last addr=10.1.1.10, ; #panics => 0 ; Not Finished
ttyUSB9 => last host=nnaida9, => last addr=10.1.1.9, ; #panics => 0 ; Not Finished |
|
283
|
Mon Jun 6 13:52:10 2016 |
TD, ML & YS | FEE64 power-cycle, FEE64 & aidas1 reboot |
21.40 toggled merge input pause state - merge pause stopped at link 18 (nnaida19 - this link is supposed
to be disabled
obtained 'unable to connect' to nnaida1 for DAQ stop
reboot aidas1, power cycle and reboot FEE64s |
|
846
|
Sun Jun 16 10:06:21 2019 |
TD, CG | FEE64 nnaida14 noise issues |
Attachments 1, 3, 5 & 7 *.L spectra log scale
Attachments 2, 4, 6 & 8 *.L spectra linear scale (expanded around pulser peak)
Attachments 9-12 *.W spectra 20us FSR
Observe
2.13.L low amplitude
2.14.L & 3.3.L large number of counts and 'sinusoidal' continuum
... but ... the corresponding waveform spectra look OK
Zero'd all histograms to confirm observations - confirmed - see attachment 16
Pulser peak width spectrum 3.8.L 71 ch FWHM |
| Attachment 1: 100.png
|
|
| Attachment 2: 101.png
|
|
| Attachment 3: 102.png
|
|
| Attachment 4: 103.png
|
|
| Attachment 5: 104.png
|
|
| Attachment 6: 105.png
|
|
| Attachment 7: 106.png
|
|
| Attachment 8: 107.png
|
|
| Attachment 9: 110.png
|
|
| Attachment 10: 111.png
|
|
| Attachment 11: 112.png
|
|
| Attachment 12: 113.png
|
|
| Attachment 13: 120.png
|
|
| Attachment 14: 121.png
|
|
| Attachment 15: 122.png
|
|
| Attachment 16: 130.png
|
|
|
935
|
Fri Dec 8 12:55:38 2023 |
TD, NH | FEE64 configuration |
FEE64 configuration for 1x MSL type BB18(DS)-1000 24cm x 8cm DSSSD
*Beam into page*
aida09 BB7 FEE64
aida05 aida01 aida06 p+n junction FEE64s
aida02 aida04 n+n Ohmic FEE64s
*
aida07 aida03 aida08 p+n junction FEE64s
* approximate position of c. 1.5cm diamond-shaped hole in black cloth optical screen positioned between 'upstream' bPlast and BB18 DSSSD. |
|
64
|
Wed Apr 22 03:33:01 2015 |
TD | FEE64 Fast Discriminator OR o/p via MACB |
Illustration of the trigger timing of the AIDA FEE64 fast discriminator OR output via the
MACB front panel Trigger outputs.
Channel 1: BNC PB-4 Pulser Trigger Output
Channel 2: BNC PB-4 Pulser Analogue Output
Channel 3: MACB Trigger Output
MACB Trigger Output: NIM complement
width ~ 7us
delay ~ 750ns (with respect to BNC PB_4 Pulser Analogue Output)
Example illustrates MAC Trigger Output from nnaida5 with standard ASIC settings and
LEC/MEC fast discriminator 0x40 |
| Attachment 1: tek00000.tif
|
|
| Attachment 2: tek00001.tif
|
|
|
68
|
Thu Apr 23 09:02:57 2015 |
TD, Patrick | FEE64 Fast Discriminator OR o/p via MACB |
> Illustration of the trigger timing of the AIDA FEE64 fast discriminator OR output via the
> MACB front panel Trigger outputs.
>
> Channel 1: BNC PB-4 Pulser Trigger Output
> Channel 2: BNC PB-4 Pulser Analogue Output
> Channel 3: MACB Trigger Output
>
> MACB Trigger Output: NIM complement
> width ~ 7us
> delay ~ 750ns (with respect to BNC PB_4 Pulser Analogue Output)
>
> Example illustrates MAC Trigger Output from nnaida5 with standard ASIC settings and
> LEC/MEC fast discriminator 0x40
It would be useful to show the Trigger signal at the different levels of the MACB distribution system... then
the difference will show the delay through the MACB layer.
Are you able to estimate the length of cable between the pulser and the adaptor boards.
What are the conclusions about the delay .... is it too much to be useful ? |
|
218
|
Wed May 11 06:00:56 2016 |
AE, VP, BM (Byul Moon) | FEE64 <-> MACB trigger mapping |
Here is the mapping of the trigger output of MAC-B modules to FEE64 modules
3.1 NNAIDA5 veto-X2
3.2 NNAIDA14 D4-X2
3.3 NNAIDA13 D5-X2
3.4 NNAIDA6 D6-X2
4.1 NNAIDA28 -
4.2 NNAIDA27 D1-Y1
4.3 NNAIDA20 D2-Y1
4.4 NNAIDA19 D3-Y1
5.1 NNAIDA12 D4-Y1
5.2 NNAIDA11 D5-Y1
5.3 NNAIDA3 veto-Y1
5.4 NNAIDA4 D6-Y1
6.1 NNAIDA25 D1-X1
6.2 NNAIDA17 D3-X1
6.3 NNAIDA18 D2-X1
6.4 NNAIDA26 -
8.1 NNAIDA29 -
8.2 NNAIDA30 D1-X2
8.3 NNAIDA22 D2-X2
8.4 NNAIDA21 D3-X2
9.1 NNAIDA15 D4-Y2
9.2 NNAIDA16 D5-Y2
9.3 NNAIDA7 D6-Y2
9.4 NNAIDA8 veto-Y2
10.1 NNAIDA1 veto-X1
10.2 NNAIDA9 D5-X1
10.3 NNAIDA10 D4-X1
10.4 NNAIDA2 D6-X1
11.1 NNAIDA23 D2-Y2
11.2 NNAIDA32 D1-Y2
11.3 NNAIDA31 -
11.4 NNAIDA24 D3-Y2
MACB modules are labeled, from left to right, according to their position in the NIM crate.
D1 is the most upstream DSSD, and veto the most downstream one. |
| Attachment 1: dssd_layout.jpg
|
|
|
357
|
Sun Sep 4 04:35:42 2016 |
TD | FEE64 & MACB configuration |
UP
nnaida1 nnaida9 nnaida17
LEFT nnaida2 nnaida10 nnaida18 RIGHT
nnaida23 nnaida15 nnaida7 nnaida3 nnaida11 nnaida19
nnaida24 nnaida16 nnaida8 nnaida4 nnaida12 nnaida20
nnaida5 nnaida13 nnaida21
nnaida6 nnaida14 nnaida22
DOWN
<LOOKING UPSTREAM>
LEFT-RIGHT n+n ohmic strips
UP-DOWN p+n junction strips
1 2 3 4 5 6 7 8 9 10 11 MACB NIM Module # spare 1 spare 2
<- #1 <- #2 <- #2 <- #2 <- #2 <- #1 <- #7 <- #7 <- #7 <- #7 Next
-> #2 -> #3 6* 21 7 23 -> #8 1 17 3 19 Port 1
-> #7 -> #4 5 22 8 24 -> #9 2 18 4 20 Port 2
-> #5 13 29 15 31 -> #10 9 25 11 27 Port 3
-> #6 14 30 16 32 -> #11 10 26 12 28 Port 4
** 2 2 3 3 3 3 3 3 3 3 Mode
y y Rev B y
* = Master Timestamp FEE64
** MACB (rev A serial #13 mode 5) external 50MHz clock
or
MACB (rev B serial #11 mode 0) internal 50MHz cloxk
MACB HDMI cabling mechanically secured by 1U cable organiser above MACB NIM bin and by AIDA frame
- see attachments 1-3 |
| Attachment 1: IMG_6502.JPG
|
|
| Attachment 2: IMG_6503.JPG
|
|
| Attachment 3: IMG_6504.JPG
|
|
|
431
|
Tue Nov 8 00:52:59 2016 |
OH, TD | FEE Settings and Options files |
Used a program to sort through the settings files located in /MIDAS/DB/EXPERIMENTS/AIDA/Settings_FIle_Name/nnaider1,2,3... and /MIDAS/DB/EXPERIMENTS/AIDA/Options.
By comparing the parameter values we got from this to the value we know they should be set to we found some discrepancies in FEEs 1 and 3-8 with values being set
to 0xd rather than the value to which they should have been saved to. This was corrected and new settings and options files were created. Last night we saw that
the DAQ is able to load these files correctly and that the values remain as they should be.
An excel sheet is attached which makes it easy to compare the values parsed by the code to the default values. To do this it is best to sort the data by FEE, then
type, then type number then parameter value number using the sort function on the data tab. After copying this data into the new settings sheet it will flag any
values that do not match the default values in red. |
| Attachment 1: FEE_Settings.xlsx
|
|
517
|
Fri Dec 2 09:47:45 2016 |
DK | F8 targets |
F8 targets, for posterity.
Plastic: 39~40 mm
Carbon: 20. mm |
|
518
|
Fri Dec 2 09:47:58 2016 |
DK | F8 targets |
F8 target measurements, for posterity.
Plastic: ~39 to 40 mm
Carbon: 20. mm |
|
487
|
Sun Nov 27 19:33:00 2016 |
Liu, PV, AE | F11 degrader setting (night Nov27-Nov28) |
Analysis of files for two more settings of F11 degrader to optimize implantation of 40Mg.
+ setting 1: from Nov 27th, 22:16
Fixed degrader: 3 mm Pb + 1 mm Al, Variable degrader: 1.3 mm W + 2 mm Al
AIDA run: R26_0 to R26_38
BigRIPS run: 40Mg1037 (partial) to 40Mg1040
see attachments: run1038_imp*png
+ setting 2: from Nov 28th, 1:38.
Entered F11 during stripper foil change and removed 1mm Al fixed degrader (same as during Nov 26th - ~ run
40Mg1012).
Fixed degrader: 3 mm Pb, Variable degrader: 1.3 mm W + 2 mm Al
AIDA run: R26_39 to ...
BigRIPS run: from 40Mg1041 to ...
see attachments: run104x_imp*png (2 hours of data: run 1041 and 1042)
Setting 2 moved implantation depth one or two strips upstream (1.2 according to calculations). 40Mg seems to be
implanted about the third strip; a conclusion with LOW STATISTICS, but consistent with the trend of how the
implantation position depends on neutron number for the higher-count isotopes.
Setting 2 seems to be our best option (at least without going into F11 and reconfiguring degraders). We will
continue accumulating data with it.
Attachments: the 1D plot shows the ion implant position (DSSD) gated for all ions and for Al and Mg gates in the
PID. The 2D plots show the PID with gates on implants in different DSSDs.
Range calculation for degrader's configuration:
https://docs.google.com/spreadsheets/d/1QJp8t98sT3pExAQb3xtHtAvk4TUDVO6alhbLIaNtx8A/edit?usp=sharing |
| Attachment 1: run1038_imp_profile.png
|
|
| Attachment 2: run1038_imp_pid.png
|
|
| Attachment 3: run104x_imp_profile.png
|
|
| Attachment 4: run104x_imp_pid.png
|
|
|
499
|
Tue Nov 29 19:07:35 2016 |
AE, CG, ATS, AT | F11 conditions after change to C target in F8 [light particles?] |
The main experiment changed to a carbon reaction target at F8 (similar thickness of CH2 previously used), and retuned the ZDS. First BigRIPS run after retuning is 40Mg_1093 (at 2:29 am, Nov 30th)
The background at F11 has increased. The neutron backgroun incresead by a factor of ~10. The rates of visual scalers also increased; for example Si Top/Bottom from about 50 Hz to 300 Hz (see attachment 1).
One possible explanation are higher light particle rate at F11. By comparing the PID for C target (attachment 2) with that of CH2 target setting (e.g. https://elog.ph.ed.ac.uk/AIDA/492), it looks like the new conditions have a higher transmission for A/Q=3 fragments (3H et al). Also, in the new setting the Si isotopes are also transmitted to F11.
The implantation depth is still good; same as we had for C target at F8 (compare 40Al distribution in attachment 3 with what we had before). |
| Attachment 1: visual_scal_4am_Cin_F7.png
|
|
| Attachment 2: pid_r1093.png
|
|
| Attachment 3: imp_ch2.png
|
|
| Attachment 4: pid_ch2.png
|
|
| Attachment 5: hits_ch2.png
|
|
|
84
|
Thu Apr 30 02:11:19 2015 |
TD | Example waveforms with heavy-ion beam |
1 - nnaida1 DSSSD#3 p+n (pulser?)
2 - nnaida1 DSSSD#3 p+n heavy ion
3 - nnaida6 DSSSD#1 p+n
4 - nnaida16 DSSSD#1 n+n
5 - nnaida14 DSSSD#2 p+n
6 - nnaida3 DSSSD#3 n+n
7 - nnaida13 DSSSD#3 p+n
50MSPS, 14-bit ADC, 1000 samples
Each trace is the most recent capture for that specific channel |
| Attachment 1: 70.png
|
|
| Attachment 2: 71.png
|
|
| Attachment 3: 72.png
|
|
| Attachment 4: 73.png
|
|
| Attachment 5: 74.png
|
|
| Attachment 6: 75.png
|
|
| Attachment 7: 76.png
|
|