Got an idea?

Please, tell us how we can make ATAS the best platform for you. Vote for other users' ideas.

Please note that this is a place only for ideas. Moderators will NOT publish:

  1. Questions and issues regarding the platform. Please write them directly to support@atas.net

  2. Posts with more than one idea.

NOTE: The post can be moderated for up to four weeks.

In Progress

Create ATAS for MAC (OS X) / Create ATAS for MAC (OS X)

Mac is one of the most used systems and its reliability, is much higher than Windows, I think it would be great to be able to use ATAS natively in MAC OS In windows, the CPU consumption is very high, I think that by the way MAC would be more efficient. Thank you See also my other suggestion: https://support.orderflowtrading.ru/communities/1/topics/21856-session-level-with-parameters Mac is one of the most commonly used systems, and its reliability is much higher than Windows. I think it would be great to be able to use ATAS on MAC OS X. Windows CPU consumption is very high, I think by the way MAC would be more efficient. Thank you See also my other suggestion: https://support.orderflowtrading.ru/communities/1/topics/21856-session-level-with-parameters

An Anonymous User Over 2 years ago

98

💡 Feature Request

In Progress

Cross-trade instruments using the following manager module

It would be nice to have the option to cross-trade instruments using the copy trade module. For instance, if I long ES in the parent account, the child account will long MES with lot size according to the set ratio in the module. Or, for instance, if I long ES in the parent account, then the child account will short NQ etc. This one may be impossible to program reliably, but it would be amazing. It would be extremely convenient to have the ability to alternate executions across multiple accounts. For instance, if I want to scale into 10 contracts across 10 accounts instead of concentrating all of that risk into one account. Every time I add contracts on the parent account, it will cycle those executions through each child account. The first contract long will execute in one account, then the next contract gets executed in the next account and so on. When I scale out, it will scale out in each account sequentially. If I add 5 contracts, it will spread those 5 contracts out across 5 accounts.

Danny Over 2 years ago

48

💡 Feature Request

Planned

Continous Futures Contracts with Back-Adjustment

Currently the contract roll-over for US indices contracts from Sep-23 to Dec-23 takes place. The price difference between both expiration months is quite high as shown in the following table: The already available continuous contracts in ATAS (with prefix #) link these contracts after the first day of higher volume in the new contract, i.e. after closing of 11/09/2023. This un-adjusted chaining of contracts leads to a big price gap which corrupts any charts of the #-contracts,I.e. any (Volume-) or Pivot-Level Analysis in #-contract is currently totally misleading in my opinion. (left: Z3 contract, right: Cont. contract) Proposal: Introduction of a second version of continuous contracts (e.g. with prefix +) with difference-adjusted historical prices for the old contracts as it is available in other charting platforms (SierraCharts, MotiveWave, NinjaTrader). The best possibility would be -in my opinion- to use the price difference of the daily mid-prices of the last active day of the old contract. In the table above this would be for ES: ((4543,50+4508,75,25)/2) - (4493,50+4459,25)/2 = 49,75 (rounded to the nearest tick if necessary). This means all historical data until EoD 11/09/2023 should be increased by 49,75 points in order to adjust the price gap to the December contract. This process would be necessary for each roll-over historically and in the future. I assume it should be easier to process this on the data servers of ATAS, this would avoid any programming work in the client software.

Joerg Over 2 years ago

38

💡 Feature Request

Planned

Risk Management Module

A Risk Management Module to track and protect the traders account. A) In this module the user can set different PARAMETERS for each account. (Maybe in $ and/or in % based on Account size) For example: - Max Daily Loss Limit - Max Weekly Loss Limit - Max Trades a Day Limit - Account Balance Limit - Daily Profit Goal B) and IF a parameter/limit is reached the trader can choose an option to protect his account. For example: - Warning Alert (Setting to modify your alarm sound) - Lock Trading for XX minutes - Close ATAS - Custom Notification / Splash-screen C) The User can Protect the Risk Management Tool with a password if he wants to change the parameters. for example: if Daily Loss is reached and the user emotionally wants to set the Loss Limit higher the Module is protected by a password, this would be an additional protection for the account.

Gabriel Over 2 years ago

53

💡 Feature Request

Editable Indicators in Atas (like Pinescript)

I think it would be a great idea to make indicators easily editable and importable by making them open source and having a script editor implemented in Atas (like pinescript for tradingview) so users can write their own indicators, or modify existing indicators and tweak them. Maybe also a good idea to make the language the same as pinescript so that you can import your own indicators (as Tradingview is the most popular and has the biggest custom indicator library) In addition it would also be nice to be able to create multiple templates for indicators, for example a template for dark mode where the line is white, and a template for white mode were the line is black.

Pjotr Over 2 years ago

7

💡 Feature Request

Numerous time zones which have a 30 or 45 minutes offset are missing

As it is known , Time is an important aspect of trading. It is vital that we set the proper time zone, so that we are able to track different market sessions and the exact time of each session's open and close. Recently, I found out that some time zones are missing in ATAS platform time zone settings. There are numerous time zones which have a 30 or 45 minutes offset, however, as you can see in the following picture, there is no option of choosing these time zone ( E.g. choosing UTC +8:45 is not possible due to the 45 minute offset) I would be thankful if ATAS's development team consider adding these missing time zone. Best Regards.

An Anonymous User Over 2 years ago

3

💡 Feature Request

Support for various Linux distributions

Linux is becoming increasingly popular as a desktop OS. Especially with the end of support for Windows 10, many people will have to decide what to do with their PC. An upgrade to Windows 11 is not possible for many users due to the hardware. There is the alternative of buying a new one or switching to a Linux distribution. With the support of Linux from ATAS, the decision becomes easier for some. Currently, I am only aware of 2 trading platforms that officially run on Linux. ATAS could be the third. With .net Core there is already a good basis for the port to other operating systems. The runtime is available for Mac as well as for various Linux distributions. The challenge is the GUI topics. Wine or Mono could be a solution for this. (https://ccifra.github.io/PortingWPFAppsToLinux/Overview.html) For distributing the software, there are now distribution independent technologies such as Flatpack (https://flatpak.org/). Flatpack ensures that the runtime environment is the same for all distributions.

Pascal About 2 years ago

12

💡 Feature Request

Enhancing ATAS Trading Platform with Customizable Exit Strategies

Currently, users have to set up their exit strategies manually each time they want to use a different approach. I propose implementing a feature that allows users to create and store multiple types of exit strategies, which can then be easily accessed and applied via a dropdown menu. The primary goal of this feature is to streamline the trading process and improve efficiency for traders using the ATAS platform. Here are the key components and benefits of implementing this feature: Customizable Exit Strategies: Users should be able to define various exit strategies based on their trading preferences and risk tolerance. This could include stop-loss (SL) and take-profit (TP) levels, trailing stops, time-based exits, and more. Save and Manage Presets: Once a user creates an exit strategy, they should have the option to save it as a preset. These presets can be named and managed by the user for easy access later. Dropdown Menu Integration: Integrate a dropdown menu within the platform's order entry or trade management interface. This dropdown will list the saved exit strategy presets, allowing users to select and apply them to their trades effortlessly. Auto-populate SL/TP Fields: When a user selects a preset from the dropdown menu, the corresponding stop-loss and take-profit levels should automatically populate the respective fields in the order entry form. This reduces the chances of manual input errors and saves time during trade execution. Flexibility and Adaptability: Traders often use different exit strategies based on market conditions, asset volatility, and trading objectives. Providing this flexibility within the platform empowers users to adapt quickly to changing market dynamics without having to reconfigure settings repeatedly. Enhanced Trading Experience: By simplifying the process of applying exit strategies, traders can focus more on analyzing market trends and making informed trading decisions rather than spending time on repetitive setup tasks. Implementing this feature aligns with ATAS's commitment to delivering a user-friendly and efficient trading platform. It enhances the platform's functionality and caters to the diverse needs of traders across various asset classes and trading styles. I believe that integrating customizable exit strategy presets with auto-population capabilities will be well-received by ATAS users and contribute positively to their overall trading experience.

SALMAN SARWAR Almost 2 years ago

16

💡 Feature Request

Local Time Zones incl. Daylight Savings for Charts

Current situation: Data are stored with UTC (Universal Time) time stamps and the user can define a static offset value on exchange or symbol basis in order to define how many hours time shift ATAS applies in chart (and tape) windows in order to display the data in local time (or whatever time the user chooses). Daylight saving time adjustments need to be implemented via an adjustment of the offset value which then is applied to the complete history shown in the chart. Problem: It is not possible to generate a chart which correctly displays historical data which consider daylight savings and contain summer times and winter times within this chart. It is necessary to decide between summer and winter time for the complete displayed time span. This leads to a partial time shift for any time-filtered indicator. e.g. Relative Volume, VWAP (with time filter), Daily Lines (with time filter), MP+TPO (with time filter) etc. In the screenshot above the US-Opening is shifted between 14:30 and 15:30 CET (Central European Time) -please see the blue vertical lines- but it applies to any exchange which does not trade in UTC time zone. Proposal: Instead of the static (UTC basis+offset) value for time zones ATAS should offer all the different local time zones incl. daylight savings (as available in windows) + offset value. This would allow to combine daylight saving periods of the exchange with the regular time shift to the local time of the user, like e.g. US-Eastern time + 6 hours (US daylight savings combined with CET time zone).

Joerg About 2 years ago

7

💡 Feature Request