<?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[Popular Topics]]></title><description><![CDATA[A list of topics that are sorted by post count]]></description><link>http://quantiacs.com/community/popular/alltime</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Jul 2026 19:26:50 GMT</lastBuildDate><atom:link href="http://quantiacs.com/community/popular/alltime.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 24 May 2024 07:27:44 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Acess previous weights]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/3328">@blackpearl</a> Hello. I don’t use machine learning in trading, and I don’t have similar examples. If you know Python and know how to develop such systems, or if you use ChatGPT (or similar tools) for development, you should not have difficulties modifying existing examples. You will need to change the model training and prediction functions.</p>
<p dir="auto">One of the competitive advantages of the Quantiacs platform is the ability to test machine learning models from a financial performance perspective.</p>
<p dir="auto">I haven’t encountered similar tools. Typically, models are evaluated using metrics like F1 score and cross-validation (for example, in the classification task of predicting whether the price will rise tomorrow).</p>
<p dir="auto">However, there are several problems:</p>

It is unclear how much profit this model can generate. In real trading, there will be commissions, slippage, data errors, and the F1 score doesn’t account for these factors.
It is possible to inadvertently look into the future. For instance, data preprocessing techniques like standardization can leak future information into the past. If you subtract the mean or maximum value from each point in the time series, the maximum value reached in 2021 would be known in 2015, which is unacceptable.

<p dir="auto">The Quantiacs platform provides a tool for evaluating models from a financial performance perspective.</p>
<p dir="auto">However, practice shows that finding a good machine learning model requires significant computational resources and time for training and testing. My results when testing strategies on real data have not been very good.</p>
]]></description><link>http://quantiacs.com/community/topic/555/acess-previous-weights</link><guid isPermaLink="true">http://quantiacs.com/community/topic/555/acess-previous-weights</guid><dc:creator><![CDATA[Vyacheslav_B]]></dc:creator><pubDate>Fri, 24 May 2024 07:27:44 GMT</pubDate></item><item><title><![CDATA[Q20 contest results]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/72">@theflyingdutchman</a> Hi, the Q20 had very few participants, less than 30, and no strategies are being traded at the moment according to the contest rules. Indeed we made no official announcement.</p>
<p dir="auto">However, the participants had the opportunity to submit the same code (provided it is correct) to the Q21 (in other words no correlations check are performed).</p>
<p dir="auto">It is very cumbersome to remove strategies from the web page, so they are currently displayed.</p>
<p dir="auto">If your strategy will continue to perform good and we believe it can be traded, we will contact you.</p>
]]></description><link>http://quantiacs.com/community/topic/535/q20-contest-results</link><guid isPermaLink="true">http://quantiacs.com/community/topic/535/q20-contest-results</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Mon, 01 Jul 2024 07:30:01 GMT</pubDate></item><item><title><![CDATA[Calculation of trading strategies]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/8">@jeppe_and</a> Thanks for the reply, i'll check my code</p>
]]></description><link>http://quantiacs.com/community/topic/254/calculation-of-trading-strategies</link><guid isPermaLink="true">http://quantiacs.com/community/topic/254/calculation-of-trading-strategies</guid><dc:creator><![CDATA[dark.pidgeot]]></dc:creator><pubDate>Fri, 16 Sep 2022 06:22:52 GMT</pubDate></item><item><title><![CDATA[Submission failure]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/20">@antinomy</a> great! Sorry, there were many submissions on the last day.</p>
]]></description><link>http://quantiacs.com/community/topic/85/submission-failure</link><guid isPermaLink="true">http://quantiacs.com/community/topic/85/submission-failure</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Mon, 07 Jun 2021 14:10:18 GMT</pubDate></item><item><title><![CDATA[Please advise on p settings. Thanks.]]></title><description><![CDATA[<p dir="auto">Hi <a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a><br />
Thank you, I'll try that.</p>
]]></description><link>http://quantiacs.com/community/topic/12/please-advise-on-p-settings-thanks</link><guid isPermaLink="true">http://quantiacs.com/community/topic/12/please-advise-on-p-settings-thanks</guid><dc:creator><![CDATA[spancham]]></dc:creator><pubDate>Wed, 17 Mar 2021 22:35:41 GMT</pubDate></item><item><title><![CDATA[Q21 submission]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a> Thank you!</p>
]]></description><link>http://quantiacs.com/community/topic/562/q21-submission</link><guid isPermaLink="true">http://quantiacs.com/community/topic/562/q21-submission</guid><dc:creator><![CDATA[Sun-73]]></dc:creator><pubDate>Thu, 29 Aug 2024 14:55:41 GMT</pubDate></item><item><title><![CDATA[Missed Call to write output]]></title><description><![CDATA[<p dir="auto">I finally resolved the issue, after lots of struggle. The custom layers, custom loss function and the function had to be serialized and deserialized correctly in order to save the architecture and weights as Json, rather than in a dictionary, like is suggested for pytorch in the Neural netowork template.<br />
It seems Pytorch is way more user friendly when it comes to saving and loading models.</p>
]]></description><link>http://quantiacs.com/community/topic/522/missed-call-to-write-output</link><guid isPermaLink="true">http://quantiacs.com/community/topic/522/missed-call-to-write-output</guid><dc:creator><![CDATA[magenta.kabuto]]></dc:creator><pubDate>Sat, 06 Apr 2024 01:27:27 GMT</pubDate></item><item><title><![CDATA[More color on contest rules]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/15">@magenta-grimer</a> Hello, the 34 M USD have been allocated to the winning strategies according to the contest rules.</p>
<p dir="auto">Other strategies have been funded, and agreements are in place between quantiacs, investors and quants. We cannot disclose more details now, sorry.</p>
<p dir="auto">5M USD is a reasonable capacity a strategy could handle, yes.</p>
]]></description><link>http://quantiacs.com/community/topic/97/more-color-on-contest-rules</link><guid isPermaLink="true">http://quantiacs.com/community/topic/97/more-color-on-contest-rules</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Tue, 24 Aug 2021 08:56:39 GMT</pubDate></item><item><title><![CDATA[Backtesting]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/229">@stefanm</a> Thank you!</p>
]]></description><link>http://quantiacs.com/community/topic/372/backtesting</link><guid isPermaLink="true">http://quantiacs.com/community/topic/372/backtesting</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Sat, 01 Apr 2023 17:51:09 GMT</pubDate></item><item><title><![CDATA[Announcement of updates to the Q21 contest]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a> Thank you very much once again!</p>
]]></description><link>http://quantiacs.com/community/topic/577/announcement-of-updates-to-the-q21-contest</link><guid isPermaLink="true">http://quantiacs.com/community/topic/577/announcement-of-updates-to-the-q21-contest</guid><dc:creator><![CDATA[Sun-73]]></dc:creator><pubDate>Tue, 18 Jun 2024 19:38:25 GMT</pubDate></item><item><title><![CDATA[backtest_ml has too long a run time]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/2784">@illustrious-felice</a></p>
<p dir="auto">Incorporating seed initialization into your PyTorch code ensures reproducibility by making the random number generation predictable. This involves setting seeds for the PyTorch engine, NumPy, and the Python random module if you're using it. Below, I'll show you how to integrate seed initialization into your existing code. Remember, while this can make your experiments more reproducible, it does not guarantee identical results across different hardware or PyTorch versions due to the inherent nondeterminism in some GPU operations.</p>
import xarray as xr  # xarray for data manipulation
import qnt.data as qndata  # functions for loading data
import qnt.backtester as qnbt  # built-in backtester
import qnt.ta as qnta  # technical analysis library
import numpy as np
import pandas as pd
import torch
from torch import nn, optim
import random

# Seed initialization function
def set_seed(seed_value=42):
    """Set seed for reproducibility."""
    random.seed(seed_value)
    np.random.seed(seed_value)
    torch.manual_seed(seed_value)
    torch.cuda.manual_seed(seed_value)
    torch.cuda.manual_seed_all(seed_value)  # if you are using multi-GPU.
    torch.backends.cudnn.deterministic = True
    torch.backends.cudnn.benchmark = False

# Set the seed for reproducibility
set_seed(42)

asset_name_all = ['NAS:AAPL', 'NAS:AMZN', 'NAS:MSFT']

class LSTM(nn.Module):
    """
    Class to define our LSTM network.
    """
    def __init__(self, input_dim=3, hidden_layers=64):
        super(LSTM, self).__init__()
        self.hidden_layers = hidden_layers
        self.lstm1 = nn.LSTMCell(input_dim, self.hidden_layers)
        self.lstm2 = nn.LSTMCell(self.hidden_layers, self.hidden_layers)
        self.linear = nn.Linear(self.hidden_layers, 1)

    def forward(self, y, future_preds=0):
        outputs = []
        n_samples = y.size(0)
        h_t = torch.zeros(n_samples, self.hidden_layers, dtype=torch.float32)
        c_t = torch.zeros(n_samples, self.hidden_layers, dtype=torch.float32)
        h_t2 = torch.zeros(n_samples, self.hidden_layers, dtype=torch.float32)
        c_t2 = torch.zeros(n_samples, self.hidden_layers, dtype=torch.float32)

        for time_step in range(y.size(1)):
            x_t = y[:, time_step, :]  # Ensure x_t is [batch, input_dim]

            h_t, c_t = self.lstm1(x_t, (h_t, c_t))
            h_t2, c_t2 = self.lstm2(h_t, (h_t2, c_t2))
            output = self.linear(h_t2)
            outputs.append(output.unsqueeze(1))

        outputs = torch.cat(outputs, dim=1).squeeze(-1)
        return outputs

def get_model():
    model = LSTM(input_dim=3)
    return model

def get_features(data):
    close_price = data.sel(field="close").ffill('time').bfill('time').fillna(1)
    open_price = data.sel(field="open").ffill('time').bfill('time').fillna(1)
    high_price = data.sel(field="high").ffill('time').bfill('time').fillna(1)
    log_close = np.log(close_price)
    log_open = np.log(open_price)
    features = xr.concat([log_close, log_open, high_price], "feature")
    return features

def get_target_classes(data):
    price_current = data.sel(field='close')
    price_future = qnta.shift(price_current, -1)

    class_positive = 1  # prices goes up
    class_negative = 0  # price goes down

    target_price_up = xr.where(price_future &gt; price_current, class_positive, class_negative)
    return target_price_up

def load_data(period):
    return qndata.stocks.load_ndx_data(tail=period, assets=asset_name_all)

def train_model(data):
    features_all = get_features(data)
    target_all = get_target_classes(data)
    models = dict()

    for asset_name in asset_name_all:
        model = get_model()
        target_cur = target_all.sel(asset=asset_name).dropna('time', 'any')
        features_cur = features_all.sel(asset=asset_name).dropna('time', 'any')
        target_for_learn_df, feature_for_learn_df = xr.align(target_cur, features_cur, join='inner')
        criterion = nn.MSELoss()
        optimiser = optim.LBFGS(model.parameters(), lr=0.08)
        epochs = 1
        for i in range(epochs):
            def closure():
                optimiser.zero_grad()
                feature_data = feature_for_learn_df.transpose('time', 'feature').values
                in_ = torch.tensor(feature_data, dtype=torch.float32).unsqueeze(0)
                out = model(in_)
                target = torch.zeros(1, len(target_for_learn_df.values))
                target[0, :] = torch.tensor(np.array(target_for_learn_df.values))
                loss = criterion(out, target)
                loss.backward()
                return loss
            optimiser.step(closure)
        models[asset_name] = model
    return models

def predict(models, data):
    weights = xr.zeros_like(data.sel(field='close'))
    for asset_name in asset_name_all:
        features_all = get_features(data)
        features_cur = features_all.sel(asset=asset_name).dropna('time', 'any')
        if len(features_cur.time) &lt; 1:
            continue
        feature_data = features_cur.transpose('time', 'feature').values
        in_ = torch.tensor(feature_data, dtype=torch.float32).unsqueeze(0)
        out = models[asset_name](in_)
        prediction = out.detach()[0]
        weights.loc[dict(asset=asset_name, time=features_cur.time.values)] = prediction
    return weights

weights = qnbt.backtest_ml(
    load_data=load_data,
    train=train_model,
    predict=predict,
    train_period=55,
    retrain_interval=55,
    retrain_interval_after_submit=1,
    predict_each_day=False,
    competition_type='stocks_nasdaq100',
    lookback_period=55,
    start_date='2024-01-01',
    build_plots=True
)


<p dir="auto">I think I won't be available next week. If you have any more questions, don’t expect an answer from me next week.</p>
]]></description><link>http://quantiacs.com/community/topic/528/backtest_ml-has-too-long-a-run-time</link><guid isPermaLink="true">http://quantiacs.com/community/topic/528/backtest_ml-has-too-long-a-run-time</guid><dc:creator><![CDATA[Vyacheslav_B]]></dc:creator><pubDate>Fri, 08 Mar 2024 16:26:54 GMT</pubDate></item><item><title><![CDATA[Struggle creating local dev environment]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/868">@dark-pidgeot</a> Hi! After the release of version qnt “0.0.402” the issue with data loading in the local environment has been resolved. The library now uses newer dependencies, including pandas version 2.2.2.</p>
]]></description><link>http://quantiacs.com/community/topic/510/struggle-creating-local-dev-environment</link><guid isPermaLink="true">http://quantiacs.com/community/topic/510/struggle-creating-local-dev-environment</guid><dc:creator><![CDATA[Vyacheslav_B]]></dc:creator><pubDate>Tue, 13 Aug 2024 05:38:55 GMT</pubDate></item><item><title><![CDATA[Different Sharpe Ratios for Multipass-Backtest and Quantiacs Mulipass Backtest]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/5">@vyacheslav_b</a> thank you!</p>
]]></description><link>http://quantiacs.com/community/topic/374/different-sharpe-ratios-for-multipass-backtest-and-quantiacs-mulipass-backtest</link><guid isPermaLink="true">http://quantiacs.com/community/topic/374/different-sharpe-ratios-for-multipass-backtest-and-quantiacs-mulipass-backtest</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Sat, 01 Apr 2023 17:50:50 GMT</pubDate></item><item><title><![CDATA[Strategy Funding]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/89">@sheikh</a> Hi,</p>


<p dir="auto">it simply means that your system should make a new global high before you are entitled for a payment. If your system makes 1000 at the end of January, 800 at the end of Februray, 900 at the end of March and 1100 at the end of April, your profit will be generated at the end of April and they will amount to 1100-100=100;</p>


<p dir="auto">no, once the system starts being traded, it will be traded in the form it was at submission time, i.e. the quant will not be allowed to update parameters/change details. Of course a submitted system can have an adaptive logic, by changing parameters according to the value of some meta-indicator. If the quant believes there is some big change to be made, it is ok to re-submit the changed system, but it will need again to accumulate a track record before being traded.</p>


]]></description><link>http://quantiacs.com/community/topic/45/strategy-funding</link><guid isPermaLink="true">http://quantiacs.com/community/topic/45/strategy-funding</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Mon, 23 Aug 2021 14:21:42 GMT</pubDate></item><item><title><![CDATA[The Q20 Contest Started]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/15">@magenta-grimer</a> hi, you can find one very simple example here:</p>
<p dir="auto"><a href="https://quantiacs.com/documentation/en/data/fundamental.html" rel="nofollow ugc">https://quantiacs.com/documentation/en/data/fundamental.html</a></p>
<p dir="auto">best regards</p>
]]></description><link>http://quantiacs.com/community/topic/390/the-q20-contest-started</link><guid isPermaLink="true">http://quantiacs.com/community/topic/390/the-q20-contest-started</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Thu, 17 Aug 2023 12:15:22 GMT</pubDate></item><item><title><![CDATA[Share the state between iterations]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/12">@support</a><br />
ok I did what <a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/20">@antinomy</a> said below and the 'state' strategy worked.<br />
<a href="https://quantiacs.com/community/topic/46/macroeconomic-data-with-quantiacs/3?_=1619554449031" rel="nofollow ugc">https://quantiacs.com/community/topic/46/macroeconomic-data-with-quantiacs/3?_=1619554449031</a></p>
<p dir="auto">However, it broke my old strategies. So he further suggested to:<br />
<a href="https://quantiacs.com/community/topic/46/macroeconomic-data-with-quantiacs/5?_=1619556376479" rel="nofollow ugc">https://quantiacs.com/community/topic/46/macroeconomic-data-with-quantiacs/5?_=1619556376479</a><br />
And my old strategies are running again.</p>
<p dir="auto">Ok, so looks like for now for all strategies without a state I have to output and pass None to weights for the state &amp; pass a state variable to the strategy.<br />
Will keep you updated. Thanks for looking into the issue.</p>
]]></description><link>http://quantiacs.com/community/topic/15/share-the-state-between-iterations</link><guid isPermaLink="true">http://quantiacs.com/community/topic/15/share-the-state-between-iterations</guid><dc:creator><![CDATA[spancham]]></dc:creator><pubDate>Tue, 27 Apr 2021 20:44:19 GMT</pubDate></item><item><title><![CDATA[ERROR! The max exposure is too high]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/20">@antinomy</a><br />
Hi! Don’t worry about leverage — it isn’t allowed on the Quantiacs platform: all user-supplied weights are automatically normalized when your strategy is saved. Here’s how that works with two instruments.<br />
Source code of the normalize function <a href="https://github.com/quantiacs/toolbox/blob/main/qnt/output.py:" rel="nofollow ugc">https://github.com/quantiacs/toolbox/blob/main/qnt/output.py:</a></p>
def normalize(output, per_asset=False):
    from qnt.data.common import ds
    output = output.where(np.isfinite(output)).fillna(0)
    if ds.TIME in output.dims:
        output = output.transpose(ds.TIME, ds.ASSET)
        output = output.loc[
            np.sort(output.coords[ds.TIME].values),
            np.sort(output.coords[ds.ASSET].values)
        ]
    if per_asset:
        output = xr.where(output &gt; 1, 1, output)
        output = xr.where(output &lt; -1, -1, output)
    else:
        s = abs(output).sum(ds.ASSET)
        if ds.TIME in output.dims:
            s[s &lt; 1] = 1
        else:
            s = 1 if s &lt; 1 else s
        output = output / s
    try:
        output = output.drop_vars(ds.FIELD)
    except ValueError:
        pass
    return output

<p dir="auto">Example with two assets</p>
import xarray as xr
from qnt.data.common import ds
from qnt.output import normalize

times  = ['2025-06-16']
assets = ['Asset1', 'Asset2']

out1 = xr.DataArray(&lsqb;&lsqb;1.5, 0.5&rsqb;&rsqb;,
                    coords={ds.TIME: times, ds.ASSET: assets},
                    dims=[ds.TIME, ds.ASSET])
print(normalize(out1).values)

out2 = xr.DataArray(&lsqb;&lsqb;0.3, -0.2&rsqb;&rsqb;,
                    coords={ds.TIME: times, ds.ASSET: assets},
                    dims=[ds.TIME, ds.ASSET])
print(normalize(out2).values)

<p dir="auto">Console output</p>
&lsqb;&lsqb;0.75 0.25&rsqb;&rsqb;
&lsqb;&lsqb; 0.3  -0.2 &rsqb;&rsqb;

<p dir="auto"><strong>Example 1:</strong> The absolute exposure is 2 &gt; 1, so every weight is divided by 2, yielding 0.75 and 0.25.</p>
<p dir="auto"><strong>Example 2:</strong> The exposure is 0.5 &lt; 1, so the scaling factor is set to 1 and the weights stay 0.3 and –0.2.</p>
<p dir="auto">In short, even if your strategy outputs more than 100 % exposure, normalize always scales it back so the total absolute exposure never exceeds 1—preventing leverage on the Quantiacs platform.</p>
]]></description><link>http://quantiacs.com/community/topic/698/error-the-max-exposure-is-too-high</link><guid isPermaLink="true">http://quantiacs.com/community/topic/698/error-the-max-exposure-is-too-high</guid><dc:creator><![CDATA[Vyacheslav_B]]></dc:creator><pubDate>Mon, 16 Jun 2025 07:34:21 GMT</pubDate></item><item><title><![CDATA[Machine Learning Strategy]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/5">@vyacheslav_b</a><br />
Thank you! 🎉 🎉</p>
]]></description><link>http://quantiacs.com/community/topic/40/machine-learning-strategy</link><guid isPermaLink="true">http://quantiacs.com/community/topic/40/machine-learning-strategy</guid><dc:creator><![CDATA[spancham]]></dc:creator><pubDate>Mon, 19 Apr 2021 15:35:37 GMT</pubDate></item><item><title><![CDATA[Why are my Q17 Strategies not running?]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="http://quantiacs.com/community/uid/68">@mwalimudan</a> Yes, we are really sorry. We did not think about these corner cases, but with cryptos, they can take place.</p>
]]></description><link>http://quantiacs.com/community/topic/278/why-are-my-q17-strategies-not-running</link><guid isPermaLink="true">http://quantiacs.com/community/topic/278/why-are-my-q17-strategies-not-running</guid><dc:creator><![CDATA[support]]></dc:creator><pubDate>Thu, 15 Sep 2022 17:41:35 GMT</pubDate></item><item><title><![CDATA[Submission Issue]]></title><description><![CDATA[<p dir="auto">Just out of curiousity I did some testing and it looks like the class actually was the culprit.<br />
I submitted a simple strategy in 2 versions, one with a class and the other with a dictionary as state. The class version was rejected (exaclty like the one from my 1st post) and the dictionary version got accepted.</p>
]]></description><link>http://quantiacs.com/community/topic/63/submission-issue</link><guid isPermaLink="true">http://quantiacs.com/community/topic/63/submission-issue</guid><dc:creator><![CDATA[antinomy]]></dc:creator><pubDate>Sat, 15 May 2021 11:19:59 GMT</pubDate></item></channel></rss>