On Fri, 6 Oct 2017, Sven Schreiber wrote:
Am 14.09.2017 um 22:09 schrieb Allin Cottrell:
> On Thu, 14 Sep 2017, Allin Cottrell wrote:
>> On Wed, 13 Sep 2017, Sven Schreiber wrote:
>>> Sorry, to avoid confusion: According to the doc there is currently
>>> already the possibility to write "null" for the specification types
>>> (For spec type 0 it's already optional.) What I mean is if this explicit
>>> "null" could also be made optional.
>> That would be a bit awkward to arrange. [...]
> OK, not really all that awkward. In git we now support dropping the "theta"
> (hyperparameter initialization) argument to mds() and mdsl() altogether,
> meaning that the initialization is automatic (as if you gave "null" for the
Could it be that the "almonp" variant was overlooked here?
I have a case here with a term mdsl(dIPL, "almonp", theta1) which works OK
like this, but which fails if I remove the explicit 'theta1' in there.
With the other spec cases it works fine.
The point here is that as things stand we're not willing to guess how
many terms you want in your Almon polynomial (while with NEAlmon and
beta there's a clear presumption of two parameters as default).