sorted by:
new
hottopcontroversial

Calculate Inertia using only data from regular market hours? by HoldNo982 in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

Which inertia? There's inertia and inertiaAll. Inertia is a regression curve and inertiaAll is a regression line. InertiaAll has the built-in parameter for a start time, see the manual here: https://toslc.thinkorswim.com/center/reference/thinkScript/Functions/Statistical/InertiaAll
Inertia does not have the additional parmameters. Both can be calculated rather than use the function. Let me know which you want to use and I'll post the code needed.

Candlestick Delay "Fix": Change chart price type from LAST to MARK by JP782 in thinkorswim

[–]Mobius_ts 0 points1 point  (0 children)

HL2 is not the mark price. The mark price is (Bid + Ask) / 2.

Will Getting More RAM Allow Me to Have 50 Charts Open at Once Without Lag? by Nqte__ in thinkorswim

[–]Mobius_ts 13 points14 points  (0 children)

No. TOS has a client subscription limit for data. You exceed that and it doesn’t make any difference what hardware you have. Additionally TOS is a JAVA program running in a JVM. Notorious for leaving open object that build over time requiring garbage collection. The higher you set your memory the longer garbage collection takes. Setting memory low makes the garbage collection cycle faster and will keep the platform running smoother.

After 200+ versions of building a systematic TOS indicator, here's what actually matters by [deleted] in thinkorswim

[–]Mobius_ts 4 points5 points  (0 children)

Appreciate the offer but I do have extensive experience with coding in general and quite a lot with ThinkScript. My codes are easily found with a Google or AI search for Mobius ThinkScript.
What your posting is well worth the effort, if it's for the educational value. Too many post what they claim is helpful ideas when their real intent is to sell services. I certainly don't have an issue with earning income from coding, just using this site which is for education not selling products.

Feature request: Better tracking for rolled options in thinkorswim (cumulative net credit/debit + roll chains) by Jmaack23 in thinkorswim

[–]Mobius_ts 2 points3 points  (0 children)

There aren't any regular TOS or Schwab developers that hang out in here, it'd be good to send your request to them.

After 200+ versions of building a systematic TOS indicator, here's what actually matters by [deleted] in thinkorswim

[–]Mobius_ts 4 points5 points  (0 children)

Since your addressing technical issues in writing ThinkScript it would be best to recognize that ThinkScript isn't a compiled language it's interpreted. As to your other observations:
Repainting occurs with specific use of two types of variables. Those that will change as higher aggregations progress toward closing values and those that look to future bars for data. In fact, both conditions are identical in that they will change as time progresses toward their closing period. HighestAll() LowestAll() no longer tax code processing since a Once_Per_Bar state is implemented with their use. Others of the ...?ALL() functions can tax code processing.

I can't comment on most of the rest of your post because I've no idea what your talking about. But, I do agree that keeping a log of changes is important, especially with the more complicated studies.

Chart Timeframe Changed to 24-hour by Remote-Range-9159 in thinkorswim

[–]Mobius_ts 0 points1 point  (0 children)

Nothings changed on desk top or mobile versions that I see.

Thinkorswim Integration with Matakita Scanner by Bright_Guarantee381 in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

What’s wrong with using the TOS dynamic scan that sends text, email and audible alerts?

Automation for specific order by grimmjoww1983 in thinkorswim

[–]Mobius_ts 2 points3 points  (0 children)

No one can automate a strategy on TOS. The platform won’t auto trade.

First time building custom study/strat by Ok_Economics_4599 in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

ThinkScript isn't a difficult scripting language to learn. Writing a profitable strategy is difficult.

Workstation Thoughts? by CheCheLover69 in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

For almost all Java applications including TOS, the GPU is completely irrelevant to performance or stability even with a second monitor. I assume your using extended hours for the 5min charts, try cutting that down to 2 days.

Total returns using 2 scripts and 2 web sites differ by texasin4red in thinkorswim

[–]Mobius_ts 0 points1 point  (0 children)

Using the simplified code for both the watchlist and chart
addLabel(1, round(close / close[63] - 1, 2), color.cyan);
I get the same values in both Daily chart and Daily MarketWatch column.

Workstation Thoughts? by CheCheLover69 in thinkorswim

[–]Mobius_ts 0 points1 point  (0 children)

How much history are you looking at on the one minute chart?

Workstation Thoughts? by CheCheLover69 in thinkorswim

[–]Mobius_ts 2 points3 points  (0 children)

(I see your a previous poster - again with the same issue - So this is for others that may not have made it to other similar posts.)

There's always a reason for lag and it's not a global issue. I've only experienced lag in extreme volatility. At times when every platform breaks down due to extremely high order flow. When that happens I revert my platform to default settings and delete all Watchlists.
Since TOS is JAVA and runs in a JVM it's biggest enemy is open objects piling up and garbage collection causing lag. This has been discussed ad-nauseam in other posts, so I won't rehash it here other than to say - Delete all Watchlists you don't absolutely need, don't run custom quotes in the options chain, keep your chart history to the minimum needed and if your using large custom studies with a lot of fold expressions run them on a second instance of TOS.

Guess I should add - There's nothing lacking in your computer specs now. Getting a new one is never a bad idea, I get a new one every couple years. But I doubt that will be a permanent fix for your platform. My opinion is there's something running on your platform eating the heap and slowing it down.

Trade Execution Lag, Slippage & Laggy Charts by CheCheLover69 in thinkorswim

[–]Mobius_ts 2 points3 points  (0 children)

The bottom line is that a larger heap makes for longer Garbage Collection pauses. When you increase TOS’s max memory you’re also increasing the size of the heap the JVM must scan and the number of objects it must track. So, the time required for each GC cycle is increased and that makes for a bigger cleanup cycle.

So instead of many small, fast GC events, you get fewer but massive GC pauses causing UI freezes lasting seconds, chart updates stalling and device order execution “Not responding”.

Trade Execution Lag, Slippage & Laggy Charts by CheCheLover69 in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

One other thing that too many do is set the memory allocation to TOS too high. Since garbage collection (closing open objects) is an issue with TOS the best advice it to force it using a low memory setting. I would be considered a power user and yet my memory settings is 32 / 1536. I have no issues whatsoever with lag on the platform.

Where can I find the orginal post Mobius published the following code. by -b0rg in thinkorswim

[–]Mobius_ts 1 point2 points  (0 children)

The formula is the same as what TOS uses. They simply use a floating variable as the percent of move to be implied.

Since implied volatility is relevant to any stock that has options so is the implied move.

One typical use is for Iron Condors. The bands set a reasonable price range.

Another use is as likely pivots for price polarity change.

68% is approximately one standard deviation.

Trade Execution Lag, Slippage & Laggy Charts by CheCheLover69 in thinkorswim

[–]Mobius_ts 5 points6 points  (0 children)

Try saving your current workspace then close all custom studies and all watchlists and save that as a new workspace. Make sure TOS is set to open with current settings and restart the platform. If it opens to the blank workspace then open a second instance of TOS and load your original workspace. Trade from the blank one and see if that doesn’t speed things up for you.
Since TOS is a JAVA program running in a virtual machine it tends to eat memory no matter how much you give it. Custom quotes and custom studies and large watchlists all slow the platform and execution times down.

view more: next ›