Navigation

    Quantiacs Community

    • Register
    • Login
    • Search
    • Categories
    • News
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Different Sharpe ratios in backtest and after submission

    Support
    3
    11
    716
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Sun-73 last edited by

      Hi @support,

      The SR of the system "Sun73_Q17_1a" is above 1 in JupyterLab (SR = 1.08), but almost half of it (SR=0.50) after submission to the Q17 contest.

      Do you have any clue on that? I am using a modified version of the example "Q17 Supervised Learning".

      Many thanks!

      S 1 Reply Last reply Reply Quote 1
      • S
        Sun-73 @Sun-73 last edited by

        I am using the "in-sample Sharpe" in the comparison above.

        A support 2 Replies Last reply Reply Quote 1
        • A
          anshul96go @Sun-73 last edited by

          @sun-73 I am also facing the same issue. I checked the submission weights and it seems the number and type of assets used in the submission are different. Also, the data seems to be different on some days.

          support 2 Replies Last reply Reply Quote 0
          • support
            support @Sun-73 last edited by

            @sun-73 Thanks for the note, we are checking, sorry for the issue. When did you submit the code? Do you see a difference in the current notebook result and current submission result?

            In other words, how long is the lag between submission time and running the notebook?

            S 1 Reply Last reply Reply Quote 0
            • support
              support @anshul96go last edited by

              @anshul96go Thank you. When did you submit the code? Do you see a difference in the current notebook result and current submission result?

              In other words, how long is the lag between submission time and running the notebook?

              1 Reply Last reply Reply Quote 0
              • S
                Sun-73 @support last edited by

                Hi @support, I backtested the system in JupyterLab two days ago and submitted on the same day. The submission went online yesterday.

                Since I am trying to use a multi-pass strategy based on the function "qnbt.backtest_ml", maybe the difference is due to difference parameters of this function considered in Jupyter and the online filters of the quantiacs website.

                Are the parameters of the function "qnbt.backtest_ml" exactly the same in those cases?

                For example, I run the code using retrain_interval=90 days. When the system is evaluated online is it retrained every day since 2014 (or every 90 days in this example)? In other words, the parameter "retrain_interval" is forced to 1 when evaluated online?

                Many thanks again!

                S support 2 Replies Last reply Reply Quote 0
                • S
                  Sun-73 @Sun-73 last edited by

                  By the way, I submitted another system yesterday, called "Sun73_Q17_1b", with an in-sample SR=2, but today the system is online in the website with an in-sample SR=0.7

                  support 1 Reply Last reply Reply Quote 0
                  • support
                    support @Sun-73 last edited by

                    @sun-73 Ok, thanks, then if you are using the backtester with the retraining option that is the reason. Can you check your notebook run using retrain_interval = 1 day?

                    1 Reply Last reply Reply Quote 0
                    • support
                      support @Sun-73 last edited by

                      @sun-73 Also here, the reason should be the retraining interval. Can you try with retraining_interval=1?

                      S 1 Reply Last reply Reply Quote 0
                      • support
                        support @anshul96go last edited by

                        @anshul96go Hi, please check answers to Sun-73. The most likely reason is the retraining option in the backtester. Are you using that version of the backtester?

                        1 Reply Last reply Reply Quote 0
                        • S
                          Sun-73 @support last edited by

                          Hi @support,

                          I modified the retraining interval to 1 day and it worked. Thank you for the help.

                          You guys rock!

                          1 Reply Last reply Reply Quote 1
                          • First post
                            Last post
                          Powered by NodeBB | Contributors
                          • Documentation
                          • About
                          • Career
                          • My account
                          • Privacy policy
                          • Terms and Conditions
                          • Cookies policy
                          Home
                          Copyright © 2014 - 2021 Quantiacs LLC.
                          Powered by NodeBB | Contributors