SQ Xのアップデート

ここからSQ Xのアップデートやニュースについて話し合うことができます。.

このトピックは「SQ4 Early Preview」から名称変更されました。古い、もはや関連のない投稿は削除され、アーカイブされます。.

ポイントは、古い、関連性のない内容からフォーラムを整理することです。.

Mark, thanks for your reply. Look forward for Build 118.

I totally agree make the updates interval be once a month to test everything properly.

マークさん、こんにちは,

I understand what you are saying, however, given the still “somewhat” buggy stage of SQX, I think it´s better to keep a rapid release cycle. First off because this brings down duplicate bug reports about the same issue – chances are higher with a longer release schedule that several people are going to report the same issues. Secondly, often the bugs that are reported right now are of crucial nature for many users. Previously they had the chance to get them fixed by waiting a max of 2 weeks, now it´s a month, that is too long in my opinion.

I fully agree to slow things down once SQX is more stable, however, right now that is not the case and even basic stuff is still broken. No one is excepting a perfect update all 4 weeks given the current stage of the software. Instead, people are looking for quick bug fixes right now. I am all for keeping it “rapid” for now with 2 weeks releases and ironing out bugs as quickly as possible. Once things settle down and are more stable, 4 weeks are fine for sure, as the reported bugs won´t be as crucial anymore as they are now.

Just my 2 cents.

An alternative to a longer 4-week release cycle would be a make the scope smaller and stick to the 2-weeks cycle. That would make it more feasible for the development team. It also allows for a quicker feedback cycle, so the important bugs will be fixed quicker. Other than that, it also has the advantages that geektrader already mentions. Just my 2 cents …

my 2 cents : 2 week cycle dosnt work . Better 4 weeks and less bugs

My 2 cents: Agree with Geektrader, Happy with the 2 Week cycle while lots of bugs to fix, even if the number of bugs fixed is smaller.

…My 2 cents…based on my  Software Development PM experience:

– Small, easy, minimum Testing and risk impact bugs – 2 week (minor) release cycle.

– Large, more complicated, greater testing and higher risk impact bugs – 4 week (minor) release cycle.

Above based on no new features in SQX until SQX has at minimum the equivalent features and offerings of SQ3.x.x and EA Wizard (Algo Wizard in SQX) .

This would provide transparency and breed confidence throughout the Client base community in the approach to have a robust, reliable and quality software product that ‘Does what it says on the box’.

Also have to agree with geektrader, stick to the 2 week cycle for the next couple of months and make fixing the existing bugs a priority, as they drop off to an acceptable level move to a longer release cycle and then start adding new features

we made a compromise for now – B118 will be released in 3 weeks – next Friday (25.2.)

I have a request – some users reported memory problems in B117, but I’m unable to reproduce them. We don’t detect any memory leak in Build 117.
In my tests SQ X works with 8 GB RAM without any problems, it runs for days without exhausting memory. I tried every setting that was sent to me.

If some of you still experience memory problems – meaning that SQ will consume all memory and produces an error message after long run – please open a bug ticket and attach your config there.

Please note that memory problem is NOT if you simply allocate too little memory to SQ – if SQ uses only 4 GB, or if you use something complicated in Retester and it is fixed by increasing available memory then this is not a problem.

The problem is only if the memory keeps on growing constantly when SQ runs for a long time.

is there any future plans i integrate Quant Analyzer into SQX?

how that was done with EA wizard and Tickdata downloader.

マーク、こんにちは,

will be Build 118 released today ?

I’m sorry, we’ll not release build 118 today. At the last moment we finally found and reproduced reason for some memory leaks – it happens only during special circumstances – and we are fixing it.

Build 118 will be released on Monday or Tuesday next week.

Partizanas – yes, functionality of QA will be integrated into SQ X, we will be adding it continually in the next builds.

@Mark, since we’re moving to updates in 4 week intervals, is there any chance we can see OVO Renko support with tick by tick testing in Build 119 now that custom timeframes are possible?

@keinc301, is there task for it ? I would put my vote to it!

I’m user of OVO as well and using it with SQX, to test on tick level would be nice option!

As I see in this case SQX should be able to import hst MT4 files generated by OVO Renko Builder.

DalFX wrote:

@keinc301, is there task for it ? I would put my vote to it! I’m user of OVO as well and using it with SQX, to test on tick level would be nice option! As I see in this case SQX should be able to import hst MT4 files generated by OVO Renko Builder.

https://roadmap.strategyquant.com/tasks/sq4_0991

Its in the to be done later section. Im just hoping now is later 🙂

And tick by tick data is the only way to test renkos accurately. Its slow but other methods can mess up testing dramatically. So rendering tick resolution on renkos has been really important for me to have an option for. Most ea’s based on renkos fail because data cant be processed accurately.

With still so many bugs even in the existing functionality (did you take a look at the bug tracker site??), this isn´t a good moment to let them add something as complicated as this. It just means a bigger mess of everything honestly. I have so many ideas as well, yet I did not add all of them to the tracker yet, simply because first the basics needs to work PERFECTLY – not just good, but PERFECT, we are trading real money here. So give them a break and wait, like all of us, with new feature requests and instead concentrate on reporting bugs on existing functionality that is broken.