clone.orderbook does not strip history#75
Open
nmatare wants to merge 2 commits intobraverock:masterfrom
Open
Conversation
…AND it kept first order in orderbook; if order was open this could produce undesirable results
…was method used; thus any changes to the clone resulted in changes to the original
Owner
|
Your second commit makes perfect sense to me to use list2env. I don't think your first commit makes sense. Just because we are splitting time can't mean that any open orders won't be processed. I believe that we need open orders to carry forward. If strip.history is TRUE, then maybe it makes sense, but it isn't clear from the patch that it only applies in that case? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The clone.orderbook function in paramsets.R does not actually strip history:
The old orderbook is assigned a new name 'cloned.portfolio.st', but the for loop continues to reference the old name, effectively voiding the strip.history = TRUE. Also, by keeping the first order with [1, ] one could potential pass an undesired open order to an attempted set of parameters, "<- list(NULL) solves this issue".
Example: