Date: Fri, 22 Mar 2024 22:21:21 -0000 Subject: Re: [sloan-25mlog 7096] 2.5m obslog 20240321 (SJD 60391) From: cscoresby@apo.nmsu.edu That's correct, Kaike. I had loaded the next design (going from expected APOGEE signal to expected BOSS signal, I realized a half-second too late I needed more exposures to complete the cluster designs.) Though the next design was not executed, all the info thinks that those exposures were for configuration 13366 when there were supposed to be for 13365. Apologies for the inconvenience, -Conner > Hello Conner, Sean, and John, > > Looks like that BOSS exposure 366471 and 366472 have > field-design-configuration information as 23440-511224-13366 while they > are actually for 23440-511223-13365. Is this correct, Conner? If so, > should John and Sean fix the fit header and related summary files for > these exposures? > > Sean: The completion criteria you put on the wiki didn’t propagated to > the new page > https://internal.sdss.org/collaboration/organization/export/wiki. Can > you please restate the criteria? > > Not sure what were sky and seeing conditions when these designs are > observed last night, looks like we got mag15(S/N^2) of 1500-2000 for 5 > minutes, and 700-900 for 15 minutes exposures. > > Thanks, > > -Kaike > >> On Mar 22, 2024, at 7:02 AM, cscoresby@apo.nmsu.edu wrote: >> >> >> APACHE POINT OBSERVATORY SDSS 2.5M >> >> OBSERVING LOG >> Thursday March 21, 2024 >> >> (SJD 60391) >> >> ---- Observing Team ---- >> >> Conner Scoresby >> Dan Oravetz (support, SDSS wiki woes) >> >> ---- Observing Plan ---- >> >> March observing plan was inaccessible due to the SDSS Wiki being taken >> down. >> >> ---- Observing Summary ---- >> >> First ~1h lost to weather due to scattered radar in the area. Observed >> from the queue, and completed the BOSS cluster design for M5. >> Intermittent clouds in the first half gave way to clear skies in the >> second half. >> >> Notes: >> >> 1. The SDSS wiki was taken offline ~between afternoon checkout and night >> operations. The other avenues to access the wiki did not have the March >> observing plans, and I was unable to include it in this log. >> >> 2. Temperature spike on sp1 detected at 03:30Z. Issue resolved itself >> almost immediately; see Engineering Issues for details >> >> 3. Completed the BOSS cluster designs for M5. >> >> 4. Several designs were observed at sdss-obs2 to verify new OS >> compatibility. I found no issues using the obs2 station. I will continue >> to use it for the next night as well. >> >> 5. Low dust counts tonight. >> >> ---- Automatic Summary ---- >> >> Time Field-Design-Conf DesignType BOSS/APOGEE Seeing Overhead >> Complete? Comment >> 03:02:12 103445-461744-13351 bright_time 1x900/1xAB 1.6" 0:00 Yes >> 03:26:21 103457-461785-13352 bright_time 1x900/1xAB 1.2" 15:03 Yes >> 03:55:33 103467-461818-13353 bright_time 1x900/1xAB 1.3" 6:55 Yes >> 04:17:29 103471-461838-13354 bright_time 1x900/1xAB 1.2" 6:53 Yes >> 04:39:50 103743-462436-13355 bright_time 1x900/1xAB 2.0" 8:04 Yes >> 05:13:17 103469-461827-13357 bright_time 1x900/1xAB 1.7" 17:38 Yes >> 05:37:04 101162-453455-13358 bright_time 1x900/1xAB 1.9" 21:39 Yes >> 06:11:56 101162-453456-13359 bright_time 2x900/2xAB 2.0" 4:42 Yes >> 06:48:30 101177-453651-13360 bright_time 1x900/1xAB 1.7" 11:39 Yes >> 07:15:19 101167-453515-13361 bright_time 1x900/1xAB 1.9" 6:34 Yes >> 07:36:40 101167-453516-13362 bright_time 1x900/1xAB 1.9" 4:17 Yes >> 07:56:06 101167-453517-13363 bright_time 1x900/1xAB 1.5" 4:29 Yes >> 08:15:24 101167-453518-13364 bright_time 1x900/1xAB 1.6" 4:35 Yes >> 08:35:07 23440-511223-13365 engineering 1x900/1xAB 1.3" 8:03 Yes >> 08:58:03 23440-511224-13366 engineering 5x900/5xAB 1.6" 6:59 Yes >> Note 1 >> 10:41:09 23440-511225-13367 engineering 3x900/3xAB 1.7" 5:00 Yes >> 11:05:51 23440-511226-13368 engineering 2x900/2xAB 1.5" 4:41 Yes >> 11:30:38 103208-460201-13369 bright_time 1x900/2xAB 1.7" 26:27 Yes >> 12:03:58 103197-460173-13370 bright_time 1x900/1xAB 1.6" 6:31 Yes >> >> 1. First two exposures correspond to the previous design (configuration >> was loaded preemptively when signal counts were still too low. See log >> body for details). > >