|
Size: 1770
Comment:
|
← Revision 4 as of 2013-08-30 16:04:18 ⇥
Size: 28
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Introduction: == .Robert Zylka has analyzed the IMBFITS data of the run with MOPSIC. He found many problems that have been partially discussed with other NIKA collaborators via emails or orally. I gather here the list of these problems and some explanations so that we have a single easily accessible place to keep track of them and correct and avoid them in the future. == Problems in the NIKA run 6 IMBFITS data == || '''Problem number''' || '''Description of the problem''' || '''Discussion''' || '''Consequence on the processing''' || '''Solution to solve or bypass it''' || || 1 || The number of "slow" and "fast" traces is given in the NCS by the sampling rates of these traces, but in the current data this is not the case any more, i.e. all the synchronization btw the coordinates and with the backend/frontend cannot be performed "NCS like". || Problem appeared with the utilization of the 8Hz slow loop; was already there but not apparent when we used the 1Hz slow loop. Problem discussed in particular between AS and RZ; it is due to various NCS synchro problems, must be solved in NCS || || || || 2 || IMBFITS corrupted (mid June) || Discussed with Xavier, problems in IMBFITS maker || no processing || re-run the IMBFITS maker; in the future skip this intermediate software conversion step, AS will create directly the IMBFITS from the raw with the help of AB C-routine || || 3 || Huge Zig-Zag in the OTF => synchronization problem || || || || || 4 || Reference pixel definition || || || || || 5 || || || || || || 6 || || || || || || 7 || || || || || || 8 || || || || || || 9 || || || || || || 10 || || || || || || 11 || || || || || || 12 || || || || || || 13 || || || || || || 14 || || || || || || 15 || || || || || |
transfered to private wiki |
transfered to private wiki