How is RData saved
Moderators: EViews Gareth, EViews Jason, EViews Steve, EViews Moderator
-
- Non-normality and collinearity are NOT problems!
- Posts: 3775
- Joined: Wed Sep 17, 2008 2:25 pm
How is RData saved
Sometime (in the last year I think), there has been a change in how .RData is saved. Series used to be saved as time series. Now they are saved as numbers with the dates put in as row names. While I think this was a good change, it would be nice to have the option of saving in the older format as well.
-
- EViews Developer
- Posts: 799
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: How is RData saved
If your frequency is supported by R time series (annual, monthly, quarterly, daily, & undated), you can ask EViews to default all of your series objects to use that instead (during a save). My guess is that this option was changed to data.frame recently on your machine?
If your workfile is not a supported R time series frequency, EViews will default back to data.frame.
If your workfile is not a supported R time series frequency, EViews will default back to data.frame.
-
- Non-normality and collinearity are NOT problems!
- Posts: 3775
- Joined: Wed Sep 17, 2008 2:25 pm
Re: How is RData saved
Makes sense, but it would be nice to also have the option on the Save dialog.
-
- EViews Developer
- Posts: 799
- Joined: Tue Sep 16, 2008 3:00 pm
- Location: Irvine, CA
Re: How is RData saved
I disagree.
Allowing you to save a workfile to RData workspace format is basically short-hand for calling XOPEN, XPUT, XRUN, & XCLOSE yourself. I would imagine most R users would be using just a single type (either data.frame or ts) and wouldn't switch between those two often. If they did, they can call XOPEN, XPUT, XRUN, & XCLOSE themselves and use the rtype option in XPUT.
Also, our Save dialog is the generic Windows Save dialog that we've slightly modified in order to support cloud drives and updating the default directory. These modifications are extremely restricted by the dialog and really wouldn't allow us to dynamically hide/show new controls based on selected save as type. Adding the R type option here would most likely require a entirely new custom Save dialog that inevitably would exhibit different behaviors (such as keyboard behavior & left tree view) as the generic Windows one - which is undesirable.
Allowing you to save a workfile to RData workspace format is basically short-hand for calling XOPEN, XPUT, XRUN, & XCLOSE yourself. I would imagine most R users would be using just a single type (either data.frame or ts) and wouldn't switch between those two often. If they did, they can call XOPEN, XPUT, XRUN, & XCLOSE themselves and use the rtype option in XPUT.
Also, our Save dialog is the generic Windows Save dialog that we've slightly modified in order to support cloud drives and updating the default directory. These modifications are extremely restricted by the dialog and really wouldn't allow us to dynamically hide/show new controls based on selected save as type. Adding the R type option here would most likely require a entirely new custom Save dialog that inevitably would exhibit different behaviors (such as keyboard behavior & left tree view) as the generic Windows one - which is undesirable.
-
- Non-normality and collinearity are NOT problems!
- Posts: 3775
- Joined: Wed Sep 17, 2008 2:25 pm
Re: How is RData saved
I believe that 100% of EViews/R users who have posted here on the topic occasionally need to save in both ways. :)
With other formats with multiple options (e.g. Excel) you have more than one choice in the drop-down. Wouldn't be hard to have two RData choices there.
With other formats with multiple options (e.g. Excel) you have more than one choice in the drop-down. Wouldn't be hard to have two RData choices there.
Who is online
Users browsing this forum: No registered users and 22 guests