This is a tough question... Strictly code-wise, it's easier to understand what's going on with descriptive variable names. Math-wise, it's easier to tie a piece of code to the corresponding parts of an equation if the variable names match up. 

In both cases, it can be hard to think about what you're looking at while also keeping the indirections/aliases in your head.

I personally still lean towards using descriptive variable names in the code, with comments tying them back to the mathematical elements. This way the code "stands alone" and can be understood without reference to the formulas in the docs. Also, if you need to introduce auxiliary helper variables or functions, you won't be tied to names like `temporary_x` or `partial_y`.

That being said, I can see the benefit of using the same naming as in the mathematical description of the algorithm too. I don't think either approach is definitively better in all cases - it depends where you want to place the emphasis and the familiarity of the audience with the problem domain.

Your point about consistency is a good one, and that's definitely an important consideration. Whichever way you decide to go, it would be helpful to include enough supporting info in the comments so that a casual reader of the code doesn't have to refer back to the README.