From: =?UTF-8?B?Sm9zw6kgU8OhbmNoZXotR2FsbGVnbw==?= Date: Tue, 20 Oct 2020 17:24:32 +0000 Subject: Re: [sloan-25mlog 5207] 2.5m obslog 20201019 (SJD 59142) --0000000000001bc5fd05b21d8139 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That error message in STUI seems to point to a problem reading the image, rather than not being able to find it. We can run some tests this afternoon but it may be worth checking the permissions. Jos=C3=A9 On Oct 20, 2020 at 08:36:19, Kaike Pan wrote: > Hi Jose, > > The guider GUI displays gcamera image but not ecamera images. For > ecamera image, it outputs an error image: > =E2=80=9Ccannot read file: No image data found=E2=80=9D. > > -Kaike > > On Oct 20, 2020, at 8:35 AM, Jos=C3=A9 S=C3=A1nchez-Gallego wrote: > > Hi Dan, Kaike, > > To confirm, did you manage to get the ecam images in the STUI widget? Wha= t > were the values of httpHost and httpPort in the settings in STUI? > > STUI grabs the guider images using an HTTP server which should be running > in the hub on port 8080. There is a webserver running on 8080 and I can g= et > the images from there, but maybe something is off due to the server > restarts. > > Thanks, > > Jos=C3=A9 > > > On Oct 20, 2020 at 04:36:23, doravetz@apo.nmsu.edu wrote: > >> >> APACHE POINT OBSERVATORY SDSS 2.5M >> >> OBSERVING LOG >> Monday October 19, 2020 >> >> (SJD 59142) >> >> ---- Observing Team ---- >> >> Kaike Pan >> Dan Oravetz >> Dmitry Bizyaev >> Jose Sanchez-Gallego >> Connor Sayres >> >> ---- Observing Plan ---- >> >> Shakedown tasks, optical collimation prep >> >> ---- Observing Summary ---- >> >> (1) We could not achieve typical engCam and gCam temperature set points. >> E.g., >> when we tried to adjust the set point to -35C (for either engCam or gCam= ) >> the >> cooler load surpassed 95% well before hitting the set point (around -20C >> or so) and then the set point automatically reset to a warmer >> temperature. When >> we ventilated and the temperature dropped at night we were able to get t= he >> engCam down to ~-25C but we still often had the cooler load increase to >> >95% and >> we had to regularly reissue the setTemp command to try and tease the >> temperature >> back toward -25C. >> >> (2) We cleaned the drive surfaces. >> >> (3) The Guide GUI was not displaying images, but instead had an error >> message: >> "Cannot read file: No image data found". We verified that the path and >> images >> next to the 'Choose' button were correct -- image data did in fact exist >> there. >> >> (4) We updated the default.dat file using the results from the mechanica= l >> collimation. We also set NCORR=3D0. >> >> (5) We completed a home/relax mirrors sequence with no problems -- >> position >> errors are listed in the Log body. >> >> (6) There is quite a bit of dust on the engCam (see, e.g., >> gimg-0014.fits). >> Could the day staff please clean it? >> >> (7) We tried to get going on optical collimation, but we discovered some >> problems before we could make any headway. Normally, the focus is around >> 0 um >> for the engCam instrument block, but this time the best focus was ~2600 >> um (even >> though we weren't collimated we were measuring ~2 to 2.5" fwhm at best >> focus, >> but actual site seeing was 1.4"). Also, we normally work about +/- 300 u= m >> from >> best focus when we're examining out-of-focus images and adjusting >> collimation, >> but tonight we had to go +/- 700 or so um from best focus to resolve the >> doughnuts and they looked much worse than usual. We did try to experimen= t >> with >> some tilts but they did not produce expected improvements. We will >> check-in with >> day staff tomorrow about the mechanical collimation results and try to >> understand why things felt so off compared to what we usually expect at >> the >> beginning of optical collimation. For reference, gimg-0099 is an example >> at best >> focus (2600 um), gimg-0100 is +500 um from focus and gimg-0101 is -500 u= m >> from >> focus. >> >> (8) When we tried to set the azimuth velocity using the new MCP Controls >> GUI, it >> didn't work quite right. We set the speed to 200000 counts/sec and the l= og >> echoed with an 'ok'. When we then moved azimuth, the speed was very clos= e >> to the >> 200000 right at the beginning, but then ramped up to near max (~500000 >> counts/sec) shortly thereafter. >> >> (9) We took azimuth and altitude fiducial data. All the altitude >> fiducials read >> well, but there were several azimuth fiducials that didn't read: 5-10, >> 13, 15, >> 17, 24, 29-34, 37, 39, 41. It's certainly plausible that the missed >> azimuth >> fiducials was related to (8) above. >> >> (10) 1 um dust count =3D dust count was around 600-800 particles/0.1 ft^= 3 >> and we >> were open for about 7 hours. >> >> ---- Observing Log ---- >> >> 12:50Z - Started ventilation. >> >> Home/Relax Mirrors >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> M1 Home/Relax >> ------------- >> home E, F: unknownReplyKey=3D"position error", "999999999, 999999999, >> 999999999, >> 999999999, 000000000, 000000000", "999999999, 999999999, 999999999, >> 999999999, 000000000, 000000000 position error" >> >> home D: unknownReplyKey=3D"position error", "999999999, 999999999, >> 999999999, >> 000000000, 999999999, 999999999", "999999999, 999999999, 999999999, >> 000000000, 999999999, 999999999 position error" >> >> home A, B, C: 0 3 i unknownReplyKey=3D"position error", "000000000, >> 000000000, >> 000000000, 999999999, 999999999, 999999999", "000000000, 000000000, >> 000000000, >> 999999999, 999999999, 999999999 position error" >> >> M2 Home >> ------- >> home D: "position error", "999999999, 999999999, 999999999, 000000000, >> 999999999" >> >> home E: "position error", "999999999, 999999999, 999999999, 999999999, >> 000000000" >> >> home A,B,C: "position error", "-000000184, 000000131, 000000012, >> 999999999, >> 999999999" >> >> 11:28Z - Stopped ventilation. Started morning cals. >> >> ---- Mirror Numbers ---- >> >> Mirror numbers after the home/relax and updates to default.dat. We forgo= t >> to >> save new Nominals in the excitement of getting on sky, but we'll grab th= em >> tomorrow and still need to complete optical collimation anyhow for new >> setmir >> values. >> >> PRIMARY: >> -------- >> Scale: 1.000000 >> >> MIGS TONIGHT NOMINAL >> Axial A: -5.2940 -8.0940 >> Axial B: -4.8950 -7.6450 >> Axial C: -5.1790 -7.9180 >> Trans D: -4.5190 -4.5060 >> Lateral E: 0.3640 0.3700 >> Lateral F: 0.5560 0.5705 >> >> GALILS >> Commanded: 11200 -1850 6850 29650 21250 21050 >> Actual: 11200 -1850 6850 29650 21250 21050 >> >> SETMIR VALUES >> PrimDesOrient: 0.0 -11.37 6.87 375.47 621.12 >> PrimOrient: 0.0 -11.4 6.58 375.38 620.77 >> >> SECONDARY: >> ---------- >> >> Focus: 0.0000 >> Air temp: 13.50 >> Altitude: 29.999996178438877 >> >> MIGS TONIGHT NOMINAL >> Axial A: -5.8150 -0.0650 >> Axial B: 0.0000 -0.0720 >> Axial C: -5.7660 -0.1030 >> Trans D: 0.2710 -0.0970 >> >> GALILS >> Commanded: 851600 831150 887450 -2250 -6950 >> Actual: 824388 806095 852810 -2250 -6950 >> >> SETMIR VALUES >> SecDesOrient: 657.0 -14.01 -2.9 12.5 114.22 >> SecOrient: 656.98 -14.05 -2.89 12.89 114.3 >> >> ---- Telescope Status ---- >> >> Status at: 10:50Z >> >> Telescope stowed at: 121.0, 30.0, 0.0 mount >> Instrument mounted: cartridge =3D engCam >> Counterweights at: >> LN2 autofill systems: Connected and turned on >> 180L LN2 dewar scales: SP1 174 lbs, 22 psi >> >> >> ---- Software Used ---- >> >> Get Versions, 10/20/20, 10:49:41 >> -- STUI software: >> STUI : 1.7.10 >> alerts : 2.0.1 >> apo : v1_11 >> boss : 5.0.1 >> -boss.specMec : 3.0.4 >> gcamera : v2_2 >> guider : 3.8.1 >> hartmann : 1.8.0 >> hub : v4.2.4 >> mcp : 1.12-10-g3766 >> -mcp.plc : 34 >> -mcp.azFiduci : v1_142 >> -mcp.altFiduc : v1_142 >> -mcp.rotFiduc : v1_142 >> platedb : 2.8.0 >> sop : 4.0.0 >> tcc : 1.4.0 >> apogee : not availble >> apogeecal : not availble >> apogeeql : v1_6_1 >> APO-local : not availble >> >> ____________________________________________________________ >> Logs of Nightly APO Activities >> https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.htm= l >> > ____________________________________________________________ > Logs of Nightly APO Activities > https://trac.sdss.org/tracmailman/browser/private/sloan-25mlog/index.html > > > --0000000000001bc5fd05b21d8139 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable That error message in STUI seems to point to a problem reading the = image, rather than not being able to find it. We can run some tests this af= ternoon but it may be worth checking the permissions.Jos=C3=A9 On Oct 20, 2020 at= 08:36:19, Kaike Pan wrote: Hi Jose,= =C2=A0 The guider GUI displays gcamera image but not ecamera images. For ec= amera image, it outputs an error image:=E2=80=9Ccanno= t read file: No image data found=E2=80=9D.=C2=A0 -KaikeOn Oct 20,= 2020, at 8:35 AM, Jos=C3=A9 S=C3=A1nchez-Gallego wrote: Hi Dan, Kaike,= To confirm, did you manage to get the ecam images in the STUI widget? What = were the values of httpHost and httpPort in the settings in STUI?STUI grabs the guider imag= es using an HTTP server which should be running in the hub on port 8080. Th= ere is a webserver running on 8080 and I can get the images from there, but= maybe something is off due to the server restarts.Thanks,Jos=C3=A9 On Oct 20, 2020 at= 04:36:23, d= oravetz@apo.nmsu.edu wrote: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0APACHE POINT OBSERVATORY SDSS 2.5M =C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0OBSERVING LOG =C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0Monday Oc= tober 19, 2020 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0(SJD 59142)---- =C2=A0Obser= ving Team ----Kaike PanDan Ora= vetzDmitry BizyaevJose Sanchez-GallegoConnor Sayres---- Observing Plan ----= Shakedown tasks, optical collimation prep---- Observing Summary ----(1) We could not achieve typical engCam and gCam temperature set po= ints. E.g.,when we tried to adjust the set point to -35C (fo= r either engCam or gCam) thecooler load surpassed 95% well b= efore hitting the set point (around -20Cor so) and then the = set point automatically reset to a warmer temperature. Whenw= e ventilated and the temperature dropped at night we were able to get theengCam down to ~-25C but we still often had the cooler load in= crease to >95% andwe had to regularly reissue the setTemp= command to try and tease the temperatureback toward -25C.(2) We cleaned the drive surfaces.(3) The Guide GUI was not displaying images, but instead h= ad an error message:"Cannot read file: No image data fo= und". We verified that the path and imagesnext to the &= #39;Choose' button were correct -- image data did in fact exist there.(4) We updated the default.dat file using the = results from the mechanicalcollimation. We also set NCORR=3D= 0.(5) We completed a home/relax mirrors seque= nce with no problems -- positionerrors are listed in the Log= body.(6) There is quite a bit of dust on the= engCam (see, e.g., gimg-0014.fits).Could the day staff plea= se clean it?(7) We tried to get going on opti= cal collimation, but we discovered someproblems before we co= uld make any headway. Normally, the focus is around 0 umfor = the engCam instrument block, but this time the best focus was ~2600 um (eve= nthough we weren't collimated we were measuring ~2 to 2.= 5" fwhm at best focus,but actual site seeing was 1.4&qu= ot;). Also, we normally work about +/- 300 um frombest focus= when we're examining out-of-focus images and adjusting collimation,but tonight we had to go +/- 700 or so um from best focus to re= solve thedoughnuts and they looked much worse than usual. We= did try to experiment withsome tilts but they did not produ= ce expected improvements. We will check-in withday staff tom= orrow about the mechanical collimation results and try tound= erstand why things felt so off compared to what we usually expect at thebeginning of optical collimation. For reference, gimg-0099 is a= n example at bestfocus (2600 um), gimg-0100 is +500 um from = focus and gimg-0101 is -500 um fromfocus.(8) When we tried to set the azimuth velocity using the new MCP = Controls GUI, itdidn't work quite right. We set the spee= d to 200000 counts/sec and the logechoed with an 'ok'= ;. When we then moved azimuth, the speed was very close to the200000 right at the beginning, but then ramped up to near max (~500000counts/sec) shortly thereafter.(9= ) We took azimuth and altitude fiducial data. All the altitude fiducials re= adwell, but there were several azimuth fiducials that didn&#= 39;t read: 5-10, 13, 15,17, 24, 29-34, 37, 39, 41. It's = certainly plausible that the missed azimuthfiducials was rel= ated to (8) above.(10) 1 um dust count =3D du= st count was around 600-800 particles/0.1 ft^3 and wewere op= en for about 7 hours.---- Observing Log ----12:50Z - Started ventilation.Home/Relax Mirrors=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3DM1 Home/Relax-----= --------home E, F: unknownReplyKey=3D"position error&qu= ot;, "999999999, 999999999, 999999999,999999999, 000000= 000, 000000000", "999999999, =C2=A0999999999, =C2=A0999999999, 999999999, =C2=A0000000000, =C2=A0000000000 position error&quo= t;home D: unknownReplyKey=3D"position er= ror", "999999999, 999999999, 999999999,000000000, = 999999999, 999999999", "999999999, =C2=A0999999999, =C2=A09999999= 99, 000000000, =C2=A0999999999, =C2=A0999999999 position err= or"home A, B, C: 0 3 i unknownReplyKey= =3D"position error", "000000000, 000000000,00= 0000000, 999999999, 999999999, 999999999", "000000000, =C2=A00000= 00000, =C2=A0000000000, 999999999, =C2=A0999999999, =C2=A099= 9999999 position error"M2 Home-------home D: "position error", "99999= 9999, 999999999, 999999999, 000000000, 999999999"home E: "position error", "999999999, 999999999, 99= 9999999, 999999999, 000000000"home A,B,C= : "position error", "-000000184, 000000131, 000000012, 99999= 9999,999999999"11:28Z - S= topped ventilation. Started morning cals.----= Mirror Numbers ----Mirror numbers after the = home/relax and updates to default.dat. We forgot tosave new = Nominals in the excitement of getting on sky, but we'll grab themtomorrow and still need to complete optical collimation anyhow for= new setmirvalues.PRIMARY:--------Scale: 1.000000MIGS TONIGHT NOMINALAxial A: -5.2940 -8.0940Axial B: -4.8950 -7.6450Axial C: -5.1790 -7.9180Trans D: -4.5190 -4.5060Lateral E: 0.3640 0.3700Lateral F: 0.5560 0.5705GALIL= SCommanded: =C2=A011200 -1850 6850 29650 21250 21050Actual: =C2=A0=C2=A0=C2=A0=C2=A011200 -1850 6850 29650 21250 21050SETMIR VALUESPrimDesOrient: 0.0 = -11.37 6.87 375.47 621.12PrimOrient: =C2=A0=C2=A0=C2=A00.0 -= 11.4 6.58 375.38 620.77SECONDARY:----------Focus: =C2=A0=C2=A0=C2=A0=C2=A0= =C2=A00.0000Air temp: =C2=A0=C2=A0=C2=A013.50= Altitude: =C2=A0=C2=A029.999996178438877MIGS = TONIGHT NOMINALAxial A: -5.8150 -0.0650Axial= B: 0.0000 -0.0720Axial C: -5.7660 -0.1030Tr= ans D: 0.2710 -0.0970GALILSCo= mmanded: 851600 831150 887450 -2250 -6950Actual: =C2=A0=C2= =A0=C2=A0824388 806095 852810 -2250 -6950SETM= IR VALUESSecDesOrient: 657.0 -14.01 -2.9 12.5 114.22SecOrient: =C2=A0=C2=A0=C2=A0656.98 -14.05 -2.89 12.89 114.3---- Telescope Status ----Status at: 10:50ZTelescope stowed at: =C2= =A0=C2=A0=C2=A0121.0, 30.0, 0.0 mountInstrument mounted: =C2= =A0=C2=A0=C2=A0=C2=A0cartridge =3D engCam =C2=A0=C2=A0Counte= rweights at: =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0LN2 autofill syst= ems: =C2=A0=C2=A0Connected and turned on180L LN2 dewar scale= s: =C2=A0SP1 174 lbs, 22 psi--= -- Software Used ----Get Versions, 10/20/20, = 10:49:41 =C2=A0-- STUI software: STUI =C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 1.7.10aler= ts =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 2.0.1apo =C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: v1_11boss =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 5.0.1-boss.specMec : 3.0.4gcamera =C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0: v2_2guider =C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0: 3.8.1hartmann =C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0: 1.8.0hub =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0: v4.2.4mcp =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0: 1.12-10-g3766-mcp.plc =C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0: 34-mcp.azFiduci : v1_142-mcp.altFiduc : v1_142-mcp.rotFiduc : v1_142platedb =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 2.8.0sop =C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 4.0.0tcc =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: 1.4= .0apogee =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: not ava= ilbleapogeecal =C2=A0=C2=A0=C2=A0=C2=A0: not availbleapogeeql =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0: v1_6_1APO-l= ocal =C2=A0=C2=A0=C2=A0=C2=A0: not availble__= __________________________________________________________Lo= gs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private/sl= oan-25mlog/index.html =20 ____________________________________________________________= Logs of Nightly APO Activities https://trac.sdss.org/tracmailman/browser/private= /sloan-25mlog/index.html =20 --0000000000001bc5fd05b21d8139--