"Simone Giannerini" <[EMAIL PROTECTED]> writes:
> My concern here is that users can be confused from the fact that if one has
> a single time series fix() uses the default method of edit() and does not
> change
> its class
>
> > x <- ts(1:5)
> > fix(x)
> > class(x)
> [1] "ts"
>
> whereas for mts
I think that a simple statement mentioning the issue in the documentation of
fix() would be helpful.
regards
Simone
On 5/9/07, Prof Brian Ripley <[EMAIL PROTECTED]> wrote:
>
> On Wed, 9 May 2007, Simone Giannerini wrote:
>
> > My concern here is that users can be confused from the fact that if
My concern here is that users can be confused from the fact that if one has
a single time series fix() uses the default method of edit() and does not
change
its class
> x <- ts(1:5)
> fix(x)
> class(x)
[1] "ts"
whereas for mts objects edit.data.frame is used so that in my opinion it
might be wort
On Wed, 9 May 2007, Simone Giannerini wrote:
> My concern here is that users can be confused from the fact that if one has
> a single time series fix() uses the default method of edit() and does not
> change
> its class
>
>> x <- ts(1:5)
>> fix(x)
>> class(x)
> [1] "ts"
>
> whereas for mts objects
Why did you expect otherwise?: fix() is treating it as matrix and
?edit.matrix says that it only works on 'simple data frames' (and converts
matrices to such).
Editing R objects can easily change aspects of them, as dput() is not
faithful, environments can get lost and so on.
On Wed, 9 May 200
Dear all,
it looks like fix() changes the class of mts objects, here is a reproducible
example (tested both on WinXP and Linux):
> x <- ts(cbind(1:5,1:5))
> x
Time Series:
Start = 1
End = 5
Frequency = 1
Series 1 Series 2
111
222
333
44
