James Chiang
James Chiang
Capturing advice from Tony (via email) on how to do this: ``` The easiest way to get this to work is just to run a jenkins agent at NERSC which...
@yymao Brian helped me set up the Jenkins job on the SLAC server, and I've made a cron job that ensures the jenkins agent at NERSC is running under the...
The script can live anywhere at NERSC where the `desc` account can access (so any `lsst` group area). You can set any environment you need within that script. The Jenkins...
Right, which is why I wondered if we needed the 90 degree shift to begin with. So if it's not a bug here, then we don't need that 90 degree...
A related issue is that `arctan(E2/E1)` doesn't necessarily get the right quadrant for the angle, so it's not clear to me that it's a useful definition since it has the...
A couple other keyword entries that [have been noted](https://lsstc.slack.com/archives/C064M4D6RC4/p1711388594005429) as missing: ``` ORIGIN TELCODE ``` `TELCODE` describes the camera, i.e., `MC` for main camera and `CC` for ComCam. `ORIGIN` describes...
Also noted during ops-rehearsal-3 preparations: the `DAYOBS` header value should be defined with a 12 hour offset applied to MJD. Details TBC. See https://rubinobs.atlassian.net/browse/DM-43495
I think it's a question of whether the observing day starts at midnight or at Noon.
The proposal is not to change MJD, but to compute DAYOBS from MJD with an offset. I don't think anyone cares about DAYOBS except the Rubin pipeines.
Some documentation on expected header keywords: https://docushare.lsst.org/docushare/dsweb/Get/LSE-400