Odometry orientation in radians is giving me weird numbers

edit

I saw that bit of documentation too. But I think the doc is wrong. Because when I change the order of params i as you suggest I get totally nonsense results. I wonder whether this is a tf vs tf2 issue?

I would implement the equation for the yaw angle from Wikipedia to be sure that this is not a problem arising from the tf / tf2. Checking the calculations with euler_from_quaternion and quaternion_from_euler with known RPY around Z axis should clear this up. Also, what exactly does "nonsense results" mean? I am using this snippet of code:

euler = euler_from_quaternion(
    [
        odometry_pose.orientation.w,
        odometry_pose.orientation.x,
        odometry_pose.orientation.y,
        odometry_pose.orientation.z,
    ]
)

without any problems...

I attempted to copy the code from Wikipedia and it matched what the Euler_from_quaternion said. I guess nonsense numbers depends on whether I have good sense. What I mean is that (lookk at the graph) it looks like if I rotate a robot 360 degrees around the z axis the quaternion reported from ODOM converts to a yaw angle that goes from -pi2 at "12 o'clock" to zero at "9 o'clock" to +pi/2 at 6, then jumps right back to -pi/2, followed by zero again at 3 to +pi/2 at 1 second after midnight and back to -pi/2. That's what I am seeing. I might have gotten something wrong, but I have double checked.

Hold on, I found a line in my code that is wrong and causing the results! Sorry, I will retract the question!

Usually, even when the solution is a fixed bug in the code, you want to leave the question and answers as they may be helpful to future readers. You should just add the information in an edit, upvote/accept the helpful comments or answers, and close the question rather than delete it.