https://pfspipe.ipmu.jp/jira This file is an XML representation of an issue en-us 8.3.4 803005 13-09-2019 https://pfspipe.ipmu.jp/jira/browse/INSTRM-2057 Instrument control development <p>Please see attached figure. The nominal position seems to consistent with the target position from FPS log. However, the final position doesn't consistent with the position found from cobra_match table. </p> INSTRM-2057

Solving the confusion between final and nominal position in pfs_config_fiber table

Task Normal Done Done arnaud.lefur chyan EngRun Wed, 16 Aug 2023 09:24:05 +0000 Wed, 30 Aug 2023 08:59:50 +0000 Wed, 30 Aug 2023 08:59:50 +0000 0 2 <p>Could you provide which cobras are problematic ? I've checked for both visits(97010, 99068) pfs_config_fiber and cobra_match tables but I don't see any inconsistencies.<br/> Eg this don't raise any exception :</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre># checking first that fiberIds do match. np.testing.assert_almost_equal(pfs_config_fiber.fiber_id.to_numpy(), cobra_match.fiber_id.to_numpy()) np.testing.assert_almost_equal(pfs_config_fiber.pfi_center_final_x_mm.to_numpy(), cobra_match.pfi_center_x_mm.to_numpy(), decimal=6) np.testing.assert_almost_equal(pfs_config_fiber.pfi_center_final_y_mm.to_numpy(), cobra_match.pfi_center_y_mm.to_numpy(), decimal=6) </pre> </div></div> <p>Ah, I found what is going on. It is a small bug from my side. </p> Development Rank 0|02qpjd:00r20060i200186403r7i3k Sprint Eng13Oct