<![CDATA[Alera Forum - All Forums]]> https://aleratrading.com/forum/ Wed, 13 May 2026 03:00:18 +0000 MyBB <![CDATA[Adding color to the Portfolio page]]> https://aleratrading.com/forum/showthread.php?tid=814 Tue, 20 Dec 2022 07:57:45 +0000 anis]]> https://aleratrading.com/forum/showthread.php?tid=814
A small suggestion from my side. It would be nice if you guys could add basic coloring (e.g. red/green for pnl and gain %) to the portfolio screen. As is, the blue font on white background is a particularly easy on the eyes.

Thanks!]]>
A small suggestion from my side. It would be nice if you guys could add basic coloring (e.g. red/green for pnl and gain %) to the portfolio screen. As is, the blue font on white background is a particularly easy on the eyes.

Thanks!]]> <![CDATA[Strategy allocation with external signal position sizing]]> https://aleratrading.com/forum/showthread.php?tid=813 Tue, 20 Dec 2022 07:54:52 +0000 anis]]> https://aleratrading.com/forum/showthread.php?tid=813
New to Alera but looks like a great platform. I'm using Amibroker to generate my signals and position sizing.

My question is about the strategy allocation. In the documentation you mention that following:

Quote:Your Strategy Allocation value does not prevent orders from being placed if they will make the strategy exceed its allocation.

Then you state that you should setup the custom lot size and max positions in order not to exceed that allocation. That assumes you want equal position sizes e.g. 10 positions of 10% each. In my case, I'm using Van Tharp's percent volatility sizing. That obviously means my position sizes will vary and I don't know how many positions it will take to fully utilize the allocation. When I ran my strategy with max positions set to 20. It opened 20 positions and the total invested exceeded the allocation. 

Can you please explain what's the purpose of the allocation if it doesn't restrict the executions? And how would I configure my settings to accomodate my variable position sizing? 

Thank you!]]>
New to Alera but looks like a great platform. I'm using Amibroker to generate my signals and position sizing.

My question is about the strategy allocation. In the documentation you mention that following:

Quote:Your Strategy Allocation value does not prevent orders from being placed if they will make the strategy exceed its allocation.

Then you state that you should setup the custom lot size and max positions in order not to exceed that allocation. That assumes you want equal position sizes e.g. 10 positions of 10% each. In my case, I'm using Van Tharp's percent volatility sizing. That obviously means my position sizes will vary and I don't know how many positions it will take to fully utilize the allocation. When I ran my strategy with max positions set to 20. It opened 20 positions and the total invested exceeded the allocation. 

Can you please explain what's the purpose of the allocation if it doesn't restrict the executions? And how would I configure my settings to accomodate my variable position sizing? 

Thank you!]]> <![CDATA[Scaling Factor]]> https://aleratrading.com/forum/showthread.php?tid=539 Thu, 21 Apr 2022 14:07:02 +0000 lethal3636]]> https://aleratrading.com/forum/showthread.php?tid=539
Can anyone describe the Scaling Factor function or direct me to a relevant thread. Nothing has appeared on search apart from the brief explanation in the Strategies section. I am wanting to scale into a position - how is this achieved exactly?

Thanks in advance,

Lee.]]>
Can anyone describe the Scaling Factor function or direct me to a relevant thread. Nothing has appeared on search apart from the brief explanation in the Strategies section. I am wanting to scale into a position - how is this achieved exactly?

Thanks in advance,

Lee.]]> <![CDATA[Reset Equity Chart]]> https://aleratrading.com/forum/showthread.php?tid=506 Tue, 08 Feb 2022 12:59:22 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=506 <![CDATA[Specifying Interactive Brokers Algos in Orders]]> https://aleratrading.com/forum/showthread.php?tid=505 Sun, 06 Feb 2022 20:34:40 +0000 admin]]> https://aleratrading.com/forum/showthread.php?tid=505 IB Algos
To learn about IB Algos see this overview and their API docs.

IB Algo JSON File
First we need to define the IB Algos we want to use in a JSON file called ibAlgos.json, which should be placed in your APM account directory. Below is an example JSON file that defines two different sets of parameters for the Adaptive IB Algo. Note that we can give each set of Algo parameters whatever name we want (adaptive1 and adaptive2 in this case), but we must fill the field algo_strategy with the correct name for the IB Algo (as specified in the IB API Docs linked above). The parameters for the IB Algo (in this case adaptivePriority) must be specified as strings (and according to IB API docs).
{
    "adaptive1": {
        "algo_strategy" : "Adaptive",
        "adaptivePriority": "Patient"
    },
    "adaptive2": {
        "algo_strategy" : "Adaptive",
        "adaptivePriority": "Urgent"
    }
}

Specifying IB Algos in Signals
To specify that an order should use an IB Algo simply add keyword ALGO followed by the name of the Algo you created. For example
BTO AAPL ALGO adaptive1
BTO SPY ALGO adaptive2

To specify the IB Algo in a CSV file, use the column ALGO.

Notes
  • You must disconnect and then reconnect APM to reflect any changes to the IB Algo file.
  • It is recommended to run some tests on a paper trading account to make sure that the orders using IB Algos are successfully placed (i.e. you should make sure the JSON file is correctly formatted and that all Algo parameters are specified)
]]> IB Algos
To learn about IB Algos see this overview and their API docs.

IB Algo JSON File
First we need to define the IB Algos we want to use in a JSON file called ibAlgos.json, which should be placed in your APM account directory. Below is an example JSON file that defines two different sets of parameters for the Adaptive IB Algo. Note that we can give each set of Algo parameters whatever name we want (adaptive1 and adaptive2 in this case), but we must fill the field algo_strategy with the correct name for the IB Algo (as specified in the IB API Docs linked above). The parameters for the IB Algo (in this case adaptivePriority) must be specified as strings (and according to IB API docs).
{
    "adaptive1": {
        "algo_strategy" : "Adaptive",
        "adaptivePriority": "Patient"
    },
    "adaptive2": {
        "algo_strategy" : "Adaptive",
        "adaptivePriority": "Urgent"
    }
}

Specifying IB Algos in Signals
To specify that an order should use an IB Algo simply add keyword ALGO followed by the name of the Algo you created. For example
BTO AAPL ALGO adaptive1
BTO SPY ALGO adaptive2

To specify the IB Algo in a CSV file, use the column ALGO.

Notes
  • You must disconnect and then reconnect APM to reflect any changes to the IB Algo file.
  • It is recommended to run some tests on a paper trading account to make sure that the orders using IB Algos are successfully placed (i.e. you should make sure the JSON file is correctly formatted and that all Algo parameters are specified)
]]> <![CDATA[Limit new trades per day]]> https://aleratrading.com/forum/showthread.php?tid=500 Wed, 26 Jan 2022 21:57:19 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=500 <![CDATA[Time stop]]> https://aleratrading.com/forum/showthread.php?tid=488 Sat, 08 Jan 2022 06:46:02 +0000 Bradsyn]]> https://aleratrading.com/forum/showthread.php?tid=488
Is there a way I can implement a time stop based on new buy orders? 

For example. I generate 10 new buy signals. Alera also knows to close them 5 days later etc?

Not sure how to go about this. I see profit target and loss stops available on the strategy tab but nothing for time stops.

Any help would be appreciated,

Brad]]>
Is there a way I can implement a time stop based on new buy orders? 

For example. I generate 10 new buy signals. Alera also knows to close them 5 days later etc?

Not sure how to go about this. I see profit target and loss stops available on the strategy tab but nothing for time stops.

Any help would be appreciated,

Brad]]> <![CDATA[Add Existing Positions to a Strategy]]> https://aleratrading.com/forum/showthread.php?tid=481 Sun, 12 Dec 2021 13:03:29 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=481 <![CDATA[Client ID]]> https://aleratrading.com/forum/showthread.php?tid=472 Fri, 26 Nov 2021 13:14:44 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=472 <![CDATA[Connection behavior with IB]]> https://aleratrading.com/forum/showthread.php?tid=468 Sat, 20 Nov 2021 06:36:19 +0000 andycare]]> https://aleratrading.com/forum/showthread.php?tid=468
If the connection with IB breaks, APM tries to reconnect with a progressively increasing time in between the retries. I think the longest time is 60 minutes, if I remember correctly. If the last reconnect fails, APM stops trying.

I’m wondering why this is implemented in this way. A reconnect doesn’t cost anything, right?

I would prefer having a fixed interval of 30 seconds to 60 seconds (maybe even adjustable) and an unlimited number of re-tries. This would prevent manual interference in some cases and lead to a better overall stability of the automated toolchain.

Thanks and regards
Andreas]]>
If the connection with IB breaks, APM tries to reconnect with a progressively increasing time in between the retries. I think the longest time is 60 minutes, if I remember correctly. If the last reconnect fails, APM stops trying.

I’m wondering why this is implemented in this way. A reconnect doesn’t cost anything, right?

I would prefer having a fixed interval of 30 seconds to 60 seconds (maybe even adjustable) and an unlimited number of re-tries. This would prevent manual interference in some cases and lead to a better overall stability of the automated toolchain.

Thanks and regards
Andreas]]> <![CDATA[Programmatically Start APM]]> https://aleratrading.com/forum/showthread.php?tid=464 Thu, 11 Nov 2021 00:33:37 +0000 admin]]> https://aleratrading.com/forum/showthread.php?tid=464
& 'C:\Program Files (x86)\Alera\Alera Portfolio Manager\Alera Portfolio Manager.exe' AccountName --start
where AccountName should be replaced by the name of the account you want to open, and the --start argument indicates that APM should connect to your broker.

Note that this was added in version 3.3.8]]>
& 'C:\Program Files (x86)\Alera\Alera Portfolio Manager\Alera Portfolio Manager.exe' AccountName --start
where AccountName should be replaced by the name of the account you want to open, and the --start argument indicates that APM should connect to your broker.

Note that this was added in version 3.3.8]]> <![CDATA[Edit PnL History]]> https://aleratrading.com/forum/showthread.php?tid=461 Fri, 05 Nov 2021 05:59:35 +0000 andycare]]> https://aleratrading.com/forum/showthread.php?tid=461
it would be great if it would be possible to edit the lines in the PnL Tab. At least being able to delete a line would also help.

The reasong for requesting that is, that I was holding DELL during the recently made split between DELL and VMW. So the log tells me, that I had a 50% loss on the DELL position, but it missed that I got VMW shares in exchange. Therefore, I see a drop in the equity curve, which didn't exist.

Furthermore, it would be great, if I could export the PnL history as CSV (or similar) in order to make further analysises.

Thanks and best regards
Andreas]]>
it would be great if it would be possible to edit the lines in the PnL Tab. At least being able to delete a line would also help.

The reasong for requesting that is, that I was holding DELL during the recently made split between DELL and VMW. So the log tells me, that I had a 50% loss on the DELL position, but it missed that I got VMW shares in exchange. Therefore, I see a drop in the equity curve, which didn't exist.

Furthermore, it would be great, if I could export the PnL history as CSV (or similar) in order to make further analysises.

Thanks and best regards
Andreas]]> <![CDATA[Remove ".au" endings]]> https://aleratrading.com/forum/showthread.php?tid=439 Mon, 27 Sep 2021 13:36:28 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=439
(gc C:\temporary\test.csv) | % {$_ -replace '.au',''} | out-file C:\temporary\test.csv -Fo -En ascii

The Powershell line works quite well, so unless other users need a feature like that, I wouldn't bother.]]>
(gc C:\temporary\test.csv) | % {$_ -replace '.au',''} | out-file C:\temporary\test.csv -Fo -En ascii

The Powershell line works quite well, so unless other users need a feature like that, I wouldn't bother.]]> <![CDATA[Remove ".au" endings]]> https://aleratrading.com/forum/showthread.php?tid=438 Mon, 27 Sep 2021 00:40:33 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=438 <![CDATA[Rounding Shares]]> https://aleratrading.com/forum/showthread.php?tid=431 Mon, 30 Aug 2021 18:45:38 +0000 Marcel]]> https://aleratrading.com/forum/showthread.php?tid=431
However, when you're working with some high priced shares, and it wants to round the value down, you end up with an order for 0 shares. For example, if you wanted to buy 4 shares of GOOG, currently around $2900 a share, it would round it up to 0. Would it be possible to include a switch to turn on the "Allow Odd Lots", only when the number of shares calculated to buy is less than a certain number, say 200 shares? Then if you have over 200 shares calculated, it would round the number of shares down.]]>
However, when you're working with some high priced shares, and it wants to round the value down, you end up with an order for 0 shares. For example, if you wanted to buy 4 shares of GOOG, currently around $2900 a share, it would round it up to 0. Would it be possible to include a switch to turn on the "Allow Odd Lots", only when the number of shares calculated to buy is less than a certain number, say 200 shares? Then if you have over 200 shares calculated, it would round the number of shares down.]]>