Dear all,

please find below a short summary of the activities of 24th on the mountain related to the AO system.

Italian people working at LBTO were:

M.Xompero, G. Brusa

March 24th

Total # of person: 2

Most of the afternoon was spent reviewing the first draft (written by Marco) of the operating manual and training the operator (Guido) for the next nights. During the night the AS behaved very well and no reset occurred, some tuning was done to improve its surface error. The general impression of the 'first user' (Guido) is that the number of GUI's required to properly monitor and run the AS is too high. It is suggested to embed the main functionalities in a single GUI (AOS GUI).

Here is a brief summary of the points discussed related to software, a detailed description is being circulated among Arcetri people.

1) we found a 'vulnerability' of the TSS management in the AOSupervisor, in some case the AOSupervisor could crash loosing the TSS control. This can be fixed by transferring this managment to the AOS module.

2) Several GUIs (AdSec Control GUI, AdOpt Control GUI, ADSCeng) can 'freeze' without notice. A proper management of these crashes is required.

3) When the AdOptControl fails to set the shell the recovery button does not work and the user is forced to go back to the AdSec Control GUI to recover from the error: this should not be needed.


around 02:00 UTC: The AS was set flat

around 03:00 UTC: The AS started applying Z4-Z11 (1 um rms wavefront) to check the relative geometry AS to primary using the w-sensor(see note1).

around 03:30 UTC: GCS stopped at Z9.

03:45 UTC: cooling inlet -3.5C, cooling outlet -1.0C, dome temperature -4.1C.

around 04:00 UTC: completed acquisition of Z9-Z11

08:16 UTC: ref. body temp. -2.0C, cooling inlet -1.2C, outlet 0.8C, dome temp. -1.8C

around 09:00 UTC: the HO mode offloading matrix was changed to >100 modes (see note 2)

11:48 UTC: flow rate 9.4 L/min; cooling inlet -0.4, cooling outlet 1.8C, RefBody +0.2C, hub -0.3C.


The following points were found about primary and secondary coordinate system:

a) the two appear to be rotated by ~10deg (related to solar tower geometry)

b) the scaling factor between the two could be off by as much as a factor of 2

c) there could be an inversion of one of the x,y axis


It was also found that the relatively high order (as seen with the active optics sensor) aberrations were proably introduced by the HO mode offloading mechanism. Increasing the cut-off from 25 to 100 modes seem to have fixed this problem.

Marco, Guido

John's email on 05/04/2010 8.08
Subj: "Typical (best I could find) guider images with static shell"
Dear AGW,
   I went mining through last week's data to find the "typical"
(best one I could find) guider image from the adaptive secondary in
static (non-adaptive) mode.  See the attached JPEGs below.

These are from 20100325 UT.
guiderimage006589.fits was 2.1 sec r' image taken at 11:41 UT. 7.5 pix FWHM = 0.41 arcsec FWHM.
guiderimage007241.fits was 0.5 sec r' image taken at 12:37 UT. 7.1 pix FWHM = 0.38 arcsec FWHM.

If you stretch them hard, you can see wings caused by the edge of the
shell.  They are fine images nonetheless.


  • Guider psf image:

  • Guider psf image:

-- ArmandoRiccardi - 05 Apr 2010
I Attachment Action Size Date Who Comment
guiderimage006589.fitsfits guiderimage006589.fits manage 47 K 05 Apr 2010 - 14:44 ArmandoRiccardi Guider psf image
guiderimage006589.jpgjpg guiderimage006589.jpg manage 13 K 05 Apr 2010 - 14:43 ArmandoRiccardi Guider psf image
guiderimage007241.fitsfits guiderimage007241.fits manage 47 K 05 Apr 2010 - 14:44 ArmandoRiccardi Guider psf image
guiderimage007241.jpgjpg guiderimage007241.jpg manage 15 K 05 Apr 2010 - 14:43 ArmandoRiccardi Guider psf image
Topic revision: r2 - 05 Apr 2010, ArmandoRiccardi
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback