SQ Xのアップデート
955件の回答
ここからSQ Xのアップデートやニュースについて話し合うことができます。.
このトピックは「SQ4 Early Preview」から名称変更されました。古い、もはや関連のない投稿は削除され、アーカイブされます。.
ポイントは、古い、関連性のない内容からフォーラムを整理することです。.
マーク
StrategyQuantアーキテクト
0
Out Of Memory – can you please open a bug task for it and attach your build settings?
With “wrong” settings you can exhaust all memory even with normal build, but I need to see the config to find out.
Drayzen – if you mean adding Minimum Net profit per week, month, year that should be fairly simple, I’ll include it into examples as well.
マーク
StrategyQuantアーキテクト
0
マークさん、こんにちは,
After upgrading from 118 to 119, All backtest results does not more match the SQ results. Tested it in MT4 & MT5. Most backtest results ends in Loss.
0
クローネックス / イヴァン・フーデツ
7年前 #239132
Quantomas – perfect nickname ☺☺☺
0
Hi Mark…
Thanks for the decision to add the ‘Envelope’ indicator (and publishing an article on how to extend SQ/AW).
Really appreciate it!
0
Drayzen – if you mean adding Minimum Net profit per week, month, year that should be fairly simple, I’ll include it into examples as well.
マークさん、こんにちは,
Yes that’s it, if you could please add an article for Net Profit per Week/Month/Year snippets that would be great, I’ve been itching to try this… 🙂
I had a look to see if I could work it out myself and I found the AvgProfitPerMonth.java file which I can see is itself fairly simple.
I thought I might be able to edit to do what I want, but it appears to have dependencies to other pre-defined functions and having no idea what other functions are available or how they all relate I figured best to leave it alone…
* The only thing I would remind is to ensure it supports negative values for the Net Profit so it’s possible to allow a specific maximum loss $ or % for each time period.
Seeing the new Community Codebase, I thought you should send out a dedicated message on social media and email direct to customers to let them know about it to get some activity and sharing of snippets, writing articles, and hopefully bring those external strategy sharing groups back to a central location…
Could you please set up an english Twitter account and cross-post (Hootsuite/Mailchimp can do this automatically) your Facebook posts as I don’t use FB any more. Twitter is also far more popular for people interested in finance.
thanks, Al
...エイリアンは人間の意見など気にも留めない...
0
マークさん、こんにちは,
I suggested a feature since Oct, 2018: https://roadmap.strategyquant.com/tasks/sq4_3149
Due to every commodities futures contracts has different rolling rules, this feature is very important to futures traders to avoid unreal data gap in backtest.
Is it possible to be done in near future?
0
why my bug report “x116 rnd logic missing” keep being ignored? for alowizard , zero response, i also ask the help question many time, still keep ignored. it has been 3 months.
0
Mark, I’m sorry for getting you wrong. It was my mistake. B119 is better than B118, thank you and SQ team what have done on this work so far.
I spent a lot of times on testing Tradestation engine recently. I reported many issues on task page, Hope they can be fixed in B120, and make it be fully reliable and workable. I’m looking forward for it.
0
SQ_IndicatorValuesExportEA.mq4
How does this EA works ?
Is there a documentation about this function ?
0
Hi Mark…
Many thanks to you and your team for adding the ‘Envelope’ indicator (and publishing an article on how to extend SQ/AW). I validated the instructions and now have the Envelope indicator in SQx/AW (with template to export to MT4 platform, etc…).
As FYI – I encountered to issues when validating the Envelope indicator in SQx via the Code Editor “Test Indicator” tab. Both issues appear cosmetic (not technical).
1. In Code Editor there are 2 “Test Indicator” tabs showing.
2. After running the test the results do not display immediately and requires to come out of “Test Indicator” tab and going back in. Eventually after a time the results appear (“Passed). Lag/Refresh issues?
Anyway…really appreciate you and your team making the Envelope indication available!
0
x116 rnd logic missing – sorry, we overlooked it, it will be fixed in the next build
SQ_IndicatorValuesExportEA.mq4 – it is an example EA that can be used to export indicator values from MT4 so that they can be compared with the values computed in SQ when you develop new indicator. It is not documented separately, you can download an example or see it described for example in article Adding Envelopes indicator – step by step example in the section MetaTraderでインジケーターデータを計算してエクスポートするにはヘルパースクリプトを使用します.
You basically have to change only the line that computes the value of your indicator.
1Trader – thank you for the report, we’ll look at these bugs
マーク
StrategyQuantアーキテクト
0
Hey @Mark Fric, is build 120 being pushed back to the end of March to fix more bugs/features or is it still being rolled out tomorrow?
0
Bug #sq4_4270: The EA generated by ALGOWIZARD after calling custom function does not add custom function code in it. – New
Hopefully this will be repaired in tonight’s version. Thank you.
0
sorry for mistake in roadmap, Build 120 will be released next Friday (29th March), not today.
I’ll check also the problem with custom functions in AlgoWizard.
マーク
StrategyQuantアーキテクト
0
やあ、マーク
I’m pretty sure 2 of the parameters in the SQx – Code – Metatrader4 – Blocks – Envelopes .tpl were not in the correct order (the 2 params are: MA_Moved and MA_Method). Refer to below for details.
Original order:
iEnvelopes(<@printInput block />, <@printParam block “#MA_Period#” />, <@printParam block “#MA_Moved#” />, <@printParam block “#MA_Method#” />, <@printParam block “#Applied_Price#” />, <@printParam block “#Deviation#” />, <@printParam block “#Line#” />+1, <@printShift block shift />)
I think the correct order should be:
iEnvelopes(<@printInput block />, <@printParam block “#MA_Period#” />, <@printParam block “#MA_Method#” />, <@printParam block “#MA_Moved#” />, <@printParam block “#Applied_Price#” />, <@printParam block “#Deviation#” />, <@printParam block “#Line#” />+1, <@printShift block shift />)
I correct and verified the above.
If you can verify yourself nd update the documentation – that would be great.
ありがとう
Kevan
0