Yesterday (March 3rd), we noticed a problem that the 200S did not run scans programmed in the scheduler. Today, Valerio and his students figured out that this is a bug in the software. The workaround for this is to have a dummy scan in the loop to fool the system in allowing the scheduler to run. In the tests that we carried out, the scans in the scheduler ran as programmed and were saved.
However, there was an issue with an earlier set of scan run by Dalek1 where only the data from scans in the loop was saved and the data from the scheduler scans was not saved. This is still not resolved and we are hoping Leosphere will respond to this quickly.
In addition, Dalek1 has been calibrated with respect to the sonics. It will be attempted to have the UTD system locate the sonics as well by tomorrow morning. Another agenda for tomorrow is to work on the focus of the UTD system to recover performance.
However, there was an issue with an earlier set of scan run by Dalek1 where only the data from scans in the loop was saved and the data from the scheduler scans was not saved. This is still not resolved and we are hoping Leosphere will respond to this quickly.
In addition, Dalek1 has been calibrated with respect to the sonics. It will be attempted to have the UTD system locate the sonics as well by tomorrow morning. Another agenda for tomorrow is to work on the focus of the UTD system to recover performance.
No comments:
Post a Comment