From: =?UTF-8?B?Sm9zw6kgU8OhbmNoZXotR2FsbGVnbw==?= Date: Wed, 9 Apr 2025 10:10:56 -0700 Subject: Re: 2.5m obslog 20250408 (SJD 60774) --0000000000007946a306325b8def Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No, I think there's no log of that but since we know the design and time at which it tried to be loaded I should be able to reproduce it with the same refraction values. I'll need to dig a bit but should be able to dump those alphas and betas. Jos=C3=A9 On Apr 9, 2025 at 10:06:18, Conor Sayres wrote: > Jos=C3=A9, > > Is there a way to find out the initial alpha/beta angles for each robot > that jaeger initially tried? If I could get to that then I could have a > closer look. My guess is there is no confsummary if the field fails to > preload? > > Conor > > > > On Apr 9, 2025, at 8:46=E2=80=AFAM, Jos=C3=A9 S=C3=A1nchez-Gallego wrote: > > From what I can see this one failed because Kaiju was not able to solve a > design collision. This is not a real collision but when Kaiju plans > trajectories for a design, if two robots are collided it will move one of > them out of the way so that the other robot (and the entire array) can > reach their destinations. This is done in jaeger by calling > > robot_grid.decollideRobot(robot_id) > > but in this case the robot remained collide after calling that method and > jaeger raised the error. Conor can probably say more. I haven't looked at > the design but this may be some pathological case and may be it could wor= k > at a different time/refraction. > > Thanks, > > Jos=C3=A9 > > > On Apr 9, 2025 at 07:27:17, Kaike wrote: > >> >> Hello Conor, John, and Jose, >> >> Can you please check the design 715630 and check why it could not be >> loaded? At the mean time, could we have Kronos NOT to schedule the desig= n >> until the issue is fixed? >> >> Thanks, >> >> -Kaike >> >> >> On Apr 9, 2025, at 6:57=E2=80=AFAM, cscoresby@apo.nmsu.edu wrote: >> >> >> Another long time sending, doing it here. >> >> >> >> APACHE POINT OBSERVATORY SDSS 2.5M >> >> >> OBSERVING LOG >> >> Tuesday April 08, 2025 >> >> >> (SJD 60774) >> >> ---- Observing Team ---- >> >> >> >> Conner Scoresby >> >> >> ---- Observing Plan ---- >> >> >> >> Tue 08 Apr 2025 60774 0.88 02:23 02:38 11:30 08:45 17:39 >> >> --- bright ( 9.7 h, w/ 0.9 h for 8 deg design) >> >> >> BOSS dither set #2 >> >> >> ---- Observing Summary ---- >> >> >> Clear and productive night. Completed the second set of BOSS dithers for >> >> this bright cycle (Design 35982). Completed 25 bright designs. >> >> >> Notes: >> >> >> 1. Design 715630 again was unable to preload. Design was skipped after o= ne >> >> instance of the error, given last night's record. >> >> >> >> > --0000000000007946a306325b8def Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No, I think there's no log of that but since we know the design and= time at which it tried to be loaded I should be able to reproduce it with = the same refraction values. I'll need to dig a bit but should be able t= o dump those alphas and betas.Jos=C3=A9 On Apr 9, 2025 at 10:06:18, Conor= Sayres wrote:= Jos=C3=A9= ,Is there a way to find out the initial alpha/beta angl= es for each robot that jaeger initially tried?=C2=A0 If I could get to that= then I could have a closer look.=C2=A0 My guess is there is no confsummary= if the field fails to preload?ConorOn Apr 9, 2025, at 8:46=E2=80=AFAM, Jos=C3=A9 S=C3=A1nch= ez-Gallego w= rote: From what I can see this one failed because Kaiju was not able to solve= a design collision. This is not a real collision but when Kaiju plans traj= ectories for a design, if two robots are collided it will move one of them = out of the way so that the other robot (and the entire array) can reach the= ir destinations. This is done in jaeger by callingrobot_grid.decollideRobot(robot_id)but in this case the robot remained col= lide after calling that method and jaeger raised the error. Conor can proba= bly say more. I haven't looked at the design but this may be some patho= logical case and may be it could work at a different time/refraction.Thanks,Jos=C3=A9 On Apr 9, 2025 at 07:27:17, Kaike= wrote: =20 Hello Conor, John, and Jose, =C2=A0Can you please check the= design 715630 and check why it could not be loaded? At the mean time, coul= d we have Kronos NOT to schedule the design until the issue is fixed?Thanks,-Kaike On Apr 9, 202= 5, at 6:57=E2=80=AFAM, cscoresby@= apo.nmsu.edu wrote: Another long time sending, doing it her= e. =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.5= M =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=A0Tuesday April 08, 2025 = =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 60774) ---- =C2=A0Observing Team ----= = Conner Scoresby ---- Ob= serving Plan ---- T= ue 08 Apr 2025 =C2=A0=C2=A0=C2=A060774 =C2=A0=C2=A00.88 =C2=A0=C2=A002:23 = =C2=A0=C2=A002:38 =C2=A011:30 =C2=A0=C2=A0=C2=A008:45 =C2=A017:39 =C2=A0 --- =C2=A0=C2=A0=C2=A0=C2=A0bright= ( 9.7 h, w/ 0.9 h for 8 deg design) BOSS dither set #2 ---- Observing Summary ----= Clear and productive night. Co= mpleted the second set of BOSS dithers for this bright cycle (Design 35982). Completed 25 bright designs. Notes: 1. Design 715630 again was unable to preload.= Design was skipped after one in= stance of the error, given last night's record. --0000000000007946a306325b8def--