#Convert to number javascript code

The second parameter is an optional parameter which is radix: If in this argument, a white space is leading, then it is ignored. If the argument which has been passed is not a string, then it is converted to a string using an operation which is called toString. So the first parameter is String, this is the value that is to be parsed. If you use inverse range there is no need for the guard.Now, explore the parameters which should be passed to this function: (oMin = oMax ? 0 : (val - oMin) * (max - min) / (oMax - oMin)) + min const rescale = (val, oMin, oMax, min, max) => Thus you should have the guard oMin = oMax to prevent the divide by zero. In JS convertValueToBoundary(5, 0, 0, 0, 100) will result in NaN rather than the expected 0 and in some languages it will throw an error. If you keep the function with the division you need to guard against divide by zero. You could also use two ranges to remove the subtraction making it even quicker const rescale = (val, oMin, invRange, min, range)=>(val - oMin) * range * invRange + min However if each range is different this would make the operation slower as you need to calculate the inverse range each time you call the function. Rescale(5, 0, 1 / 10, 0, 100) // result 50 is slower as need the / and * Your example convertValueToBoundary(5, 0, 10, 0, 100) // Output -> 50 const rescale = (val, oMin, invRange, min, max)=>(val - oMin) * (max - min) * invRange + min This would improve the performance if you were converting many values from the same range. The only optimization possible is to remove the division (multiplication is quicker than division).

#Convert to number javascript code

To further remove code noise use an arrow function and shorten the argument names const rescale = (val, oMin, oMax, min, max)=>(val - oMin) * (max - min) / (oMax - oMin) + min return (number - oldMin) * (newMax - newMin) / (oldMax - oldMin) + newMin return (((number - oldMin) * (newMax - newMin)) / (oldMax - oldMin)) + newMin However I would never guess what this function did without some extra information The function name is too long convertValueToBoundary the conversion is implied and value is commonly shortened to val so valToBoundary is less noisy. Your naming and code style make the code very noisy. The conversion should be conducted without the use of any native language functions as I plan to use the same formula across different languages and platforms. Given a scenario where this needs to execute multiple times in rapid succession, it would be ideal to have this execute with the least amount of arithmetic operations required. Is this the optimal way to conduct this calculation? After a number of different attempts the above formula is the best I could come up with. Return (((number - oldMin) * (newMax - newMin)) / (oldMax - oldMin)) + newMinįormula newValue = (((oldValue - oldMinimum) * (newMaximum - newMinimum)) / (oldMaximum - oldMinimum)) + newMinimumįor instance, given the number 5 within a range of 0-10, we want to increase the numerical range to be between 0-100 instead. * int The original number converted to the new boundary.įunction convertValueToBoundary(number, oldMin, oldMax, newMin, newMax) * int newMax The new maximium value to convert to. * int newMin The new minimum value to convert to. I have a function that takes a specific number and a range, and re-scales it to the corresponding number in a different range.