Message-ID: <56F25858.3000904@vodafone.it>
Date: 2016-03-23T08:48:24Z
From: Diego Peroni
Subject: need apply.paramset logging
In-Reply-To: <56F255AF.6080200@braverock.com>
Thanks Brian
Diego
On 23/03/2016 09:37, Brian G. Peterson wrote:
> On 03/23/2016 02:46 AM, Diego Peroni wrote:
>> I'm trying to override "apply.paramset" function to define my nested
>> custom "combine" function in it as you suggested to me.
>>
>> I got this error:
>>
>> Error in apply.paramset(qs.strategy, paramset.label = "MACDOPT",
>> portfolio = qs.strategy, :
>> could not find function "must.have.args"
>>
>> I've understood that "must.have.args" (and others in
>> quantstrat/R/utils.R) is a local function that is not exported from
>> quantstrat package.
>>
>> Is there a way to pass my custom "combine" function to "apply.paramset"?
>>
>> Or, more in general, how can I override "apply.paramset" without failing
>> with private functions in it?
>> How can I export private functions to use them?
>
> In either case, you'll have to rebuild the package with your modified
> function in it or with a modified NAMESPACE file which changes the
> exports.
>
> In any event, as I told you yesterday, it would likely be more
> valuable for you to examine the audit environment created up to the
> point that apply.paramset's included combine function fails to figure
> out where your strategy is failing.
>
>
>
>