Rapid evaluation of Daubechies Scaling function












0














Let the Daubechies 4-tap scaling function $phiin C_{0}([0,3])$ be defined by
begin{align}
phi(x) &= frac{1+sqrt{3}}{4} phi(2x) + frac{3+sqrt{3}}{4}phi(2x-1) + frac{3-sqrt{3}}{4} phi(2x-2) + frac{1-sqrt{3}}{4}phi(2x -3) \
phi(1) &= frac{1+sqrt{3}}{2} qquad phi(2) = frac{1-sqrt{3}}{2}
end{align}

This definition allows us to compute $phi$ on the dyadic numbers $mathbb{D}_{j}$ (numbers of the form $k/2^{j}$), but to evaluate any $x in mathbb{D}_{j}$, first the values from all previous levels must be evaluated and stored, making this algorithm require $mathcal{O}(2^{j})$ storage. If we are to recover even float precision, storage requirements become truly obscene. If instead of storing all possible floats in the interval $(0,3)$, we store $j_{max}$ levels, and then interpolate, we trade some storage for computation, but since the 4-tap scaling function is only continuous (not differentiable), smooth interpolators do the wrong thing, and (from numerical experiments I've performed) linear interpolation is really not that much help.



Another option is proposed here, equation 120:
begin{align*}
phi(n/2^{m}) = sum_{ell_1, ell_2,cdots, ell_m} 2^{m/2}h_{ell_1}h_{ell_2}cdots h_{ell_m}phi(n- 2^{m-1}ell_1 - 2^{m-2} ell_2 -cdots 2ell_{m-1} - ell_{m})
end{align*}

This requires no storage, but requires $4^{m}$ computations. For a 32 bit float, the worst case is $4^{23}$ operations.



Are there more efficient algorithms to evaluate $phi$?










share|cite|improve this question





























    0














    Let the Daubechies 4-tap scaling function $phiin C_{0}([0,3])$ be defined by
    begin{align}
    phi(x) &= frac{1+sqrt{3}}{4} phi(2x) + frac{3+sqrt{3}}{4}phi(2x-1) + frac{3-sqrt{3}}{4} phi(2x-2) + frac{1-sqrt{3}}{4}phi(2x -3) \
    phi(1) &= frac{1+sqrt{3}}{2} qquad phi(2) = frac{1-sqrt{3}}{2}
    end{align}

    This definition allows us to compute $phi$ on the dyadic numbers $mathbb{D}_{j}$ (numbers of the form $k/2^{j}$), but to evaluate any $x in mathbb{D}_{j}$, first the values from all previous levels must be evaluated and stored, making this algorithm require $mathcal{O}(2^{j})$ storage. If we are to recover even float precision, storage requirements become truly obscene. If instead of storing all possible floats in the interval $(0,3)$, we store $j_{max}$ levels, and then interpolate, we trade some storage for computation, but since the 4-tap scaling function is only continuous (not differentiable), smooth interpolators do the wrong thing, and (from numerical experiments I've performed) linear interpolation is really not that much help.



    Another option is proposed here, equation 120:
    begin{align*}
    phi(n/2^{m}) = sum_{ell_1, ell_2,cdots, ell_m} 2^{m/2}h_{ell_1}h_{ell_2}cdots h_{ell_m}phi(n- 2^{m-1}ell_1 - 2^{m-2} ell_2 -cdots 2ell_{m-1} - ell_{m})
    end{align*}

    This requires no storage, but requires $4^{m}$ computations. For a 32 bit float, the worst case is $4^{23}$ operations.



    Are there more efficient algorithms to evaluate $phi$?










    share|cite|improve this question



























      0












      0








      0







      Let the Daubechies 4-tap scaling function $phiin C_{0}([0,3])$ be defined by
      begin{align}
      phi(x) &= frac{1+sqrt{3}}{4} phi(2x) + frac{3+sqrt{3}}{4}phi(2x-1) + frac{3-sqrt{3}}{4} phi(2x-2) + frac{1-sqrt{3}}{4}phi(2x -3) \
      phi(1) &= frac{1+sqrt{3}}{2} qquad phi(2) = frac{1-sqrt{3}}{2}
      end{align}

      This definition allows us to compute $phi$ on the dyadic numbers $mathbb{D}_{j}$ (numbers of the form $k/2^{j}$), but to evaluate any $x in mathbb{D}_{j}$, first the values from all previous levels must be evaluated and stored, making this algorithm require $mathcal{O}(2^{j})$ storage. If we are to recover even float precision, storage requirements become truly obscene. If instead of storing all possible floats in the interval $(0,3)$, we store $j_{max}$ levels, and then interpolate, we trade some storage for computation, but since the 4-tap scaling function is only continuous (not differentiable), smooth interpolators do the wrong thing, and (from numerical experiments I've performed) linear interpolation is really not that much help.



      Another option is proposed here, equation 120:
      begin{align*}
      phi(n/2^{m}) = sum_{ell_1, ell_2,cdots, ell_m} 2^{m/2}h_{ell_1}h_{ell_2}cdots h_{ell_m}phi(n- 2^{m-1}ell_1 - 2^{m-2} ell_2 -cdots 2ell_{m-1} - ell_{m})
      end{align*}

      This requires no storage, but requires $4^{m}$ computations. For a 32 bit float, the worst case is $4^{23}$ operations.



      Are there more efficient algorithms to evaluate $phi$?










      share|cite|improve this question















      Let the Daubechies 4-tap scaling function $phiin C_{0}([0,3])$ be defined by
      begin{align}
      phi(x) &= frac{1+sqrt{3}}{4} phi(2x) + frac{3+sqrt{3}}{4}phi(2x-1) + frac{3-sqrt{3}}{4} phi(2x-2) + frac{1-sqrt{3}}{4}phi(2x -3) \
      phi(1) &= frac{1+sqrt{3}}{2} qquad phi(2) = frac{1-sqrt{3}}{2}
      end{align}

      This definition allows us to compute $phi$ on the dyadic numbers $mathbb{D}_{j}$ (numbers of the form $k/2^{j}$), but to evaluate any $x in mathbb{D}_{j}$, first the values from all previous levels must be evaluated and stored, making this algorithm require $mathcal{O}(2^{j})$ storage. If we are to recover even float precision, storage requirements become truly obscene. If instead of storing all possible floats in the interval $(0,3)$, we store $j_{max}$ levels, and then interpolate, we trade some storage for computation, but since the 4-tap scaling function is only continuous (not differentiable), smooth interpolators do the wrong thing, and (from numerical experiments I've performed) linear interpolation is really not that much help.



      Another option is proposed here, equation 120:
      begin{align*}
      phi(n/2^{m}) = sum_{ell_1, ell_2,cdots, ell_m} 2^{m/2}h_{ell_1}h_{ell_2}cdots h_{ell_m}phi(n- 2^{m-1}ell_1 - 2^{m-2} ell_2 -cdots 2ell_{m-1} - ell_{m})
      end{align*}

      This requires no storage, but requires $4^{m}$ computations. For a 32 bit float, the worst case is $4^{23}$ operations.



      Are there more efficient algorithms to evaluate $phi$?







      reference-request computational-mathematics wavelets






      share|cite|improve this question















      share|cite|improve this question













      share|cite|improve this question




      share|cite|improve this question








      edited Nov 21 '18 at 19:49







      user14717

















      asked Nov 21 '18 at 19:36









      user14717user14717

      3,8281020




      3,8281020






















          0






          active

          oldest

          votes











          Your Answer





          StackExchange.ifUsing("editor", function () {
          return StackExchange.using("mathjaxEditing", function () {
          StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
          StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
          });
          });
          }, "mathjax-editing");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "69"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          noCode: true, onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmath.stackexchange.com%2fquestions%2f3008223%2frapid-evaluation-of-daubechies-scaling-function%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Mathematics Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          Use MathJax to format equations. MathJax reference.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmath.stackexchange.com%2fquestions%2f3008223%2frapid-evaluation-of-daubechies-scaling-function%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          'app-layout' is not a known element: how to share Component with different Modules

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          WPF add header to Image with URL pettitions [duplicate]