Closed jeanconn closed 4 years ago
is this a branch of annie? master? the release in ska3-flight?
I have not reproduced this error yet.
I'm pretty sure this was the release in ska3-flight (annie 0.7).
ok, annie tests pass on testr ska3-flight when including the changes for issue #20, so it must be another manifestation of ra being np.array(ra) instead of float(ra).
I've got Quaternion 3.5.0 in 2020.1 which should have that "fix for issues #20 and #21" in there, but I'm still getting all these annie failures.
@javierggt I'm not sure why we ended up with different test results for the annie + Quaternion 3.5.0 combination, but I'm inclined to pull Quaternion from the 2020.1 release at this point. annie tests passed in my 2020.1 test build if I just downgraded Quaternion to 3.4.1 .
Ok. I'll take a look again
self = <annie.sky.Sky object at 0x7ff83d8ba630>, yag_min = array([-172.10364793])
yag_max = array([ 167.99106916]), zag_min = array([-166.61184139]), zag_max = array([ 172.34511973])
The fact that these are single-element arrays shape=(1,)
instead of scalars suggests the Quaternion bug related to output shape is not fixed in the code that was run. So either the bug fix is not complete or the wrong version of Quaternion was running somehow.
After the keynote I'll look to see if the built 3.5.0 conda package (in the repo) does not include the fix somehow.
On Tue, Jan 21, 2020, 9:08 AM Tom Aldcroft notifications@github.com wrote:
self = <annie.sky.Sky object at 0x7ff83d8ba630>, yag_min = array([-172.10364793]) yag_max = array([ 167.99106916]), zag_min = array([-166.61184139]), zag_max = array([ 172.34511973])
The fact that these are single-element arrays shape=(1,) instead of scalars suggests the Quaternion bug related to output shape is not fixed in the code that was run. So either the bug fix is not complete or the wrong version of Quaternion was running somehow.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/sot/Quaternion/issues/21?email_source=notifications&email_token=AAGBHVFKUVWCS6XEOYL5LCTQ636UNA5CNFSM4JF34XP2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEJP3JDY#issuecomment-576697487, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGBHVH4UWO3F5ICO2ZYRVDQ636UNANCNFSM4JF34XPQ .
It looks like Quaternion still needs the previous shape bugfix for yaw
(and ra0
if we care).
Also not sure if we care about roll0
.
I suppose it wouldn't be the same fix; _get_zero
looks to be adding a dimension to val. Previously this was stripped off at the end. I don't know if we want to just check shape in _get_zero
or handle in ra0 and roll0.
Also, I'm still not sure if we want a patch and Quaternion 3.5.1 for 2020.1, but hopefully LR won't be tomorrow.
Given this and that both of you are in a workshop today (and Javier through the week), I think that dropping the Quaternion 3.5.0 update for 2020.1 makes sense. We can get it in for the next release.
Either way. I'm still waiting for packages from ACIS to do final integration testing so if a fix is done before that it can probably go too. I'll plan to release 2020.1 to community/mpweekly tomorrow.
It isn't immediately clear to me how this is a Quaternion issue but this is the only difference in the environment that causes tests including this one to now fail