Generated robot model with 'null' lead to an error

[REALMagguan]

Hello!
In some of the robot's joints, there are no positional limits defined. For example, Kinova Gen3 7Dof arm. This causes the configuration generated by Pinocchio to interpret them as two separate entities, leading to errors in my planning algorithm.
To address this, I modified these joints to standard rotational joints in the URDF file(type="revolute"), but with very large limits (e.g., <limit lower="-314.159" upper="314.159").
However, the actual FK code generated now contains some 'null' characters, as shown in the attachment. I am unsure what these 'null' values represent. In addition, I have modified these limits lower(e.g., <limit lower="12.566" upper="12.566"), still did not work.
Could you please provide some insight into this issue?

Thanks.

[zkingston]

Interesting, I'm not sure why it is inserting null. Can you provide us the robot description file and config you used in a zip file? Changing from continuous to revolute should work. I would also recommend in general not using too big a range - instead, limit it to [-pi, pi] or [-2pi, 2pi].

[REALMagguan]

I have already solved this problem. It was a mistake. I forgot the negative sign - when defining the upper and lower limits.
After add negative sign -，these values became normal ones.
It is very useful to change a continuous joint into a revolute joint with a larger upper and lower limit.
And I tested various upper and lower limit values, which seemingly had no effect on this value.
Is this value descale_configuration_block related to the difference between the upper and lower limits of the joint?