This reminds me that the whole Dr. SUS situation never got taken care of. Where I left off, I was having issues pulling 40m data with NDS2 (which is what all the diagonalization scripts use).
What is the deal with 40m+NDS2? If it is till no-go, can we have a consensus on whether this is too important to wait for? If so, I will rewrite the scripts to use NDS and we can upgrade to NDS2 once we can prove we know how to use it.
| Quote: |
|
While Kiwamu and I were trying to investigate the the vertex glitches we were noticing excess noise in ITMX, which Kiwamu blamed on some sort of bad diagonalization. Sure enough, the ITMX input matrix is in the default state [0], not a properly diagonalized state. Looking through the rest of the suspensions, I found PRM also in the default state, not diagonalized.
We should do another round of suspension diagonalization.
Kiwamu (or whoever is here last tonight): please run the free-swing/kick script (/opt/rtcds/caltech/c1/scripts/SUS/freeswing) before you leave, and I'll check the matrices and update the suspensions tomorrow morning.
[0]
| 0.25 |
0.25 |
0.25 |
0.25 |
0 |
| 1.66 |
1.66 |
-1.66 |
1.66 |
0 |
| 1.66 |
-1.66 |
-1.66 |
1.66 |
0 |
| 0 |
0 |
0 |
0 |
1 |
|
|