<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Weights different in testing and submission]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a></p>
<p dir="auto">The strategy submitted to the Q17 is giving different weights after submission and in the testing phase. For instance, the q17_2 strategy is giving non-negative weights to all assets on 01/01/2014 when I cloned the strategy and run the code on the Quantiacs server whereas the weights I downloaded from the q17_2 submitted log give negative weight to some assets on 01/01/2014. Could you please help me with that?</p>
]]></description><link>http://quantiacs.com/community/topic/203/weights-different-in-testing-and-submission</link><generator>RSS for Node</generator><lastBuildDate>Sun, 12 Apr 2026 02:47:48 GMT</lastBuildDate><atom:link href="http://quantiacs.com/community/topic/203.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 19 Apr 2022 01:31:14 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Weights different in testing and submission on Fri, 22 Apr 2022 15:30:34 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/20">@antinomy</a> thanks!</p>
]]></description><link>http://quantiacs.com/community/post/676</link><guid isPermaLink="true">http://quantiacs.com/community/post/676</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Fri, 22 Apr 2022 15:30:34 GMT</pubDate></item><item><title><![CDATA[Reply to Weights different in testing and submission on Thu, 21 Apr 2022 19:42:15 GMT]]></title><description><![CDATA[<p dir="auto">About the slicing error, I had that too a while ago. It took me some time to figure out that it wasn't enough to have the right pandas version in the environment. Because I had another python install with the same version in my PATH, the qntdev-python also looked there and always used the newer pandas. So I placed the -s flag everywhere the qntdev python is supposed to run (PyCharm, Jupyter, terminal) like this</p>
<pre><code>/path/to/quantiacs/python -s strategy.py
</code></pre>
<p dir="auto">Of course one could simply remove the other python install from PATH but I needed it there.</p>
]]></description><link>http://quantiacs.com/community/post/675</link><guid isPermaLink="true">http://quantiacs.com/community/post/675</guid><dc:creator><![CDATA[antinomy]]></dc:creator><pubDate>Thu, 21 Apr 2022 19:42:15 GMT</pubDate></item><item><title><![CDATA[Reply to Weights different in testing and submission on Thu, 21 Apr 2022 16:12:38 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/21">@anshul96go</a> It looks some conflict is going on there, can you check which version of pandas are you using? It has to be 1.2.5.</p>
<p dir="auto">Maybe try to create a new environment using:</p>
<p dir="auto">conda create -n qntdev quantiacs-source::qnt conda-forge::ta-lib conda-forge::pandas==1.2.5 conda-forge::dash==1.18 python==3.7</p>
]]></description><link>http://quantiacs.com/community/post/672</link><guid isPermaLink="true">http://quantiacs.com/community/post/672</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Thu, 21 Apr 2022 16:12:38 GMT</pubDate></item><item><title><![CDATA[Reply to Weights different in testing and submission on Thu, 21 Apr 2022 11:52:45 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a> Thanks for the help team! Ahh, that makes sense. I am trying to run it.</p>
<p dir="auto">Also, there is one more issue coming up. On creating a local development environment today, the load data function is failing with the following error: "cannot represent labeled-based slice indexer for dimension 'time' with a slice over integer positions; the index is unsorted or non-unique". Could you please look into that too?</p>
]]></description><link>http://quantiacs.com/community/post/669</link><guid isPermaLink="true">http://quantiacs.com/community/post/669</guid><dc:creator><![CDATA[anshul96go]]></dc:creator><pubDate>Thu, 21 Apr 2022 11:52:45 GMT</pubDate></item><item><title><![CDATA[Reply to Weights different in testing and submission on Wed, 20 Apr 2022 14:08:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/21">@anshul96go</a> Hello, are you using the backtester with retraining option? Can you try setting the retraining interval to 1 day?</p>
]]></description><link>http://quantiacs.com/community/post/668</link><guid isPermaLink="true">http://quantiacs.com/community/post/668</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Wed, 20 Apr 2022 14:08:16 GMT</pubDate></item></channel></rss>