Why does legacy code scale variables by 2^16?
이전 댓글 표시
I am trying to understand some legacy Matlab code, and was puzzled to note that many variables are multiplied or divided by 2^16. After some digging I found this is the largest number that a 16-bit (unsigned) integer can hold, see here. I believe the code originated in C or C#. I have two questions: (1) Could the code author be using this factor to force the variable to be a float? (2) If so, can I delete all the 2^16 factors without affecting the values in Matlab?
Here is an example,
SOME_THRESHOLD = floor(0.010 * 65536); % Author's comment indicates this is supposed to represent 10%
SOME_THRESHOLD gets passed in to a function which where all the other variables have been multiplied by either 65536 or 2^16 prior to arithmetic operations; floor and abs are also used.
댓글 수: 7
Rik
2017년 11월 20일
This really depends on the code itself. Usually Matlab will be backwards compatible, but that really depends on the code itself.
KAE
2017년 11월 20일
Walter Roberson
2017년 11월 20일
It might be a storage matter: the authors might have stored as 16 bit but rescale for actual calculation.
Also, if the code is doing image processing work, it is common to rescale the pixel values to the range 0 to 1 before doing the calculation, as doing so can cut down on intermediate rescaling and overflow checks. Some of the algorithms having to do with colorspace conversion are defined in terms of the range 0 to 1.
Image Analyst
2017년 11월 20일
Care to share the code so we can comment more precisely? Or else ask the author why they did it.
Image Analyst
2017년 11월 21일
I don't see the example in your original/edited question. But ... good luck though.
Christoph F.
2017년 11월 22일
I think the original author tried to make the MatLAB script use exactly the same numbers as the C code would.
채택된 답변
추가 답변 (0개)
카테고리
도움말 센터 및 File Exchange에서 Matrix Indexing에 대해 자세히 알아보기
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!