Vertical Speed, Climb Rate redundant? Also units

In the Mission Planner, there appear to be two flight parameters which are redundant - Vertical Speed and Climb Rate. Moreover, the units displayed for both parameters always reflect the Speed Units chosen in the Planner parameters, even if those units are not particularly relevant. For example, I'm not sure that if users have chosen to display speed in mph, that they necessarily want rate of climb displayed in these units. I may be wrong, but it is my understanding that in full-scale aviation, rate of climb is always expressed in per-minute units, never per-hour units. I actually prefer per-second units. While I suggest that you seek the consensus of the user community on this issue, my vote would be for units of either feet per minute or meters per minute, or perhaps per-minute units on one (Climb Rate) and per-second units on the other (Vertical Speed) so user can choose which one to display in the "Quick" tab - but never miles-per-hour, which is almost impossible to make use of in actual flying.

Start by reviewing how Vertical Speed and Climb Rate are presented in Mission Planner, especially the Quick tab and the Planner speed-unit settings. The issue does not name files or tests and proposes several alternatives, so first seek user-community consensus on whether to consolidate the parameters and which per-minute or per-second units should be used; completion cannot be defined until that choice is made.

Written by the indexing model from the issue text.