Open tterasaki opened 5 months ago
This particular obs' bad data is some kind of obsdb bug that needs to be resolved (I can tell because the Book M_index.yaml does record the hwp stats).
I think loading more detailed hwp info, at the extended-obsdb level, is a really good idea... however, if/when you do that, please make include the direction of rotation somehow! That's a big thing we'll want to use for grouping and selecting data.
Hi, This obs predates the inclusion of hwp_freq in the update_obsdb search (see issue #777, issue #672, and PR #780) I made an up to date version of the obsdbs for satp1 and satp3 on March 28th, located in /so/home/aeadler/updated_obsdb on the site computing. We can either merge it with the current obsdbs or I can run a new update of those files.
When you load data of obs_id = 'obs_1710588251_satp3_1111111'
It looks the HWP was spinning in the run.
But when you load the obsdb, the hwp speed is set to be none:
So I would like to suggest that manifest db of hwp_angle have column of
hwp_freq_mean
andhwp_freq_stdev
in itself. As I am doing in pwv database (https://github.com/simonsobs/sotodlib/blob/3b6cc16603b08019289b44567ea7afe1fd6ffd83/sotodlib/site_pipeline/make_cosamp_hk.py#L267-L278). And make it queryable with the new query style which I am PR-ing (https://github.com/simonsobs/sotodlib/pull/856/files).