Tim, This is an approach that could perhaps be taken more often with libraries in general: Expose relevant internal (previously private) variables for the user who wishes to do additional calculations.
Maybe the library could even be structured so that if a user does that, the code for further/final calculations in the "usual" application is not compiled?
I'm still semi-illiterate about library details and conventions so this is just conjecture.