Search | User Listing Vidsite | Calendars | Quotes
Home Page ->  Optimizing OmniVest -> Smart Sizing -> View ThreadLogon (or Register, or Join TradeTight)

You are logged in as a limited-access Guest.To join TradeTight, first read the info in the Organization & Content room, then click the link above. 

Psalm 128:1-2 (NKJV) … Blessed is every one who fears the Lord, who walks in His ways. When you eat the labor of your hands, you shall be happy, and it shall be well with you. 

Implementing Position Sizing in OVest
Jump to page : 1
Now viewing page 1 [50 msgs/pg]
Jump to room :
Posted 6/3/2014 11:17 AM (#5885)
Subject: Implementing Position Sizing in OVest


Posts: 3922
USA: GA, Lawrenceville
At Ed's request, I've put together a spec for integration of Position Sizing in OVest. He had that as a "colored block" in his slide re near term OVest improvements at the end of the Bash presentation on Monday.

I'm attaching the spec, for anyone who might be interested.

I gave a very comprehensive presentation on Sat afternoon to about 35 people at the hotel, which explained how to do SmartSizing and LiquiTurns filtering, complete with robust OScripts for use in OVest and OT. So, the groundwork to utilize this has been laid.

The spec does not address how this needs to be folded in to the new OVest Portfolio Builder+Balancer (PBB) that Steve and Mark have developed, but it's clear that it should be part of that, since it potentially has a huge impact on the Equity curve. So, I've copied them with this, and hope it will be folded in - ie an OScript field for the user to spec a rule for position sizing.

Thread moved by JimDean on 8/4/2014 8:48 AM from Markets & Methods > OmniVest, Money Mgmt & Risk Control > Implementing Position Sizing in OVest

Attachments Adding Position Sizing to OVest Architecture.rtf (10KB - 71 downloads)
Top of the page Bottom of the page
Jump to page : 1
Now viewing page 1 [50 msgs/pg]
( E-mail a Link | Printer Version | Search Room )

Owner of site: Jim Dean -- Forum content is confidential, and may not be distributed without written permission.