I am using a reflecting pyramid strategy for my trades (see attached): because of restrictions in WLP (changing the size of share holdings in an account) I have to use WLP to generate the appropriate buy signals and then pas the resuts on to a VS2010 app to monitor price targets, position sizing and complete the work. Is there a way to meet my requirements entirely within WLP
Size:
Color:
There's "always a way", but it's not necessarily easy. I don't understand the requirements anyway. What attachment? Explain the requirement more precisely.
Size:
Color:
Size:
Color:
That link to your C: drive isn't going to help. You'll need to upload the document to a server and provide that link. Or, just copy and paste the text here.
Size:
Color:
sorry Cone I sent you a URL
Size:
Color:
Cone were you able to download the pdf from the server?
Size:
Color:
No.
QUOTE:
sorry Cone I sent you a URL
How did you send it to me? Can you just post the requirements here, please?
Size:
Color:
Size:
Color:
Size:
Color:
Understood Eugene I'm alreading into 200K code lines on my side - I will test a) and b) based on your code examples I had problems with splitting and pyrmiding in the past but I will take a second look.
Thanks
Size:
Color:
QUOTE:
Can WLP be modified to allow the system to
a) add shares to or> Add shares by creating a new Position. Your code must manage all Positions.
b) subtract shares from an existing position in> Use SplitPosition to split a Position into percentage parts.
c) specific quantities as> You can only deal in percentages when splittign because the script does not actually work with actual Share sizes - only Position objects, of which Shares is a property.
d) specific price levels are achieved? > Sure, no problem
All of this should take closer to 200 lines of code than 200K!
I see the "Reflecting Pyramid" requirement. You'll need to either a) write a PosSizer to create progressively larger Positions, or, b) use the WealthScript Override (SetShareSize) option to create the sizing in the script. PosSizers are the preferred route, especially since you can reuse them. Either way, your script shouldn't need to split Positions for the Reflecting Pyramid. You only need to keep track of which Position is the 1st, 2nd, or 3rd. Then you exit them in reverse order. Again, the size of the Positions are handled separately.
Size:
Color:
Thanks, and agreed I should not have to split the positions --- managing 1st, 2nd and 3rd levels reflects the the design best. (This represents a small but important fragment of the total requirements and yes, this will easly fit into 200 lines of code :-) momentum analysis, adaptation, ranking rotation and reporting requires additional code lines)
Size:
Color:
Although true reflecting pyramid is not even considered for a PosSizer, in a future release of the
Pyramiding PosSizer we'll have both the upright (already available) pyramid and a new type: reverse pyramid, at least making it more flexible.
Size:
Color:
Size:
Color: