>> 2. For displacement scaling, another reference hSize is needed (which >> is independent from the "mechanically reference" hSize), which is >> called a bit confusingly just refHSize in the current code, and which >> is set (a) when refHSize sub 1. is set and (b) when required by the >> user (the utils.setRefSe3 and such). > All algorithms I can imagine only need current hSize, the only exception > could be for display. In "disp. scaling" do you refer to homoDeform (in > that case, no, this scaling only needs hSize and velGrad) or scaled > rendering (in that case, perhaps simply use invTrsf*hSize?). > It's clear for me now. You were speaking of graphical scaling. I agree with how it is now.
B. _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
