2:59 p.m.
Ignacio writes:
I think may be useful to have a command that clears the series
in the dataset without deleting from memory the currently
defined matrices. This will do easier to deal with data in
different disagregation periods.
It can be also convenient to have a text command equivalent to
/File/clear dataset, and another text command equivalent to
/File/Append data
The simple point first: the "append" command does what
/File/Append data does.
As for clearing data, I've put some experimental things is place.
For the script equivalent of "/File/Clear data set" I've added a
"clear" argument to the "dataset" command. That is, you say
dataset clear
But this has a "preserve" option:
dataset clear --preserve
which has the effect that existing named matrices are not
destroyed.
Similarly, the commands "open" and "nulldata" have a --preserve
option: clear most stuff out, but keep matrices.
At present the --preserve option does not have a GUI counterpart.
Allin.
8:58 a.m.
El Tuesday 05 February 2008 20:59:23 Allin Cottrell escribió:
Ignacio writes:
> I think may be useful to have a command that clears the series
> in the dataset without deleting from memory the currently
> defined matrices. This will do easier to deal with data in
> different disagregation periods.
>
> It can be also convenient to have a text command equivalent to
> /File/clear dataset, and another text command equivalent to
> /File/Append data
The simple point first: the "append" command does what
/File/Append data does.
Ok.
As for clearing data, I've put some experimental things is place.
For the script equivalent of "/File/Clear data set" I've added a
"clear" argument to the "dataset" command. That is, you say
dataset clear
But this has a "preserve" option:
dataset clear --preserve
which has the effect that existing named matrices are not
destroyed.
Similarly, the commands "open" and "nulldata" have a --preserve
option: clear most stuff out, but keep matrices.
Thank you. That is perfect !
I checked the option with three commands (dataset, nulldata and open) and all
of them works very well. I am sure it is a very very usefull feature.
--
Ignacio Diaz-Emparanza
DEPARTAMENTO DE ECONOMÍA APLICADA III (ECONOMETRÍA Y ESTADÍSTICA)
UPV/EHU
Avda. Lehendakari Aguirre, 83 | 48015 BILBAO
T.: +34 946013732 | F.: +34 946013754
www.et.bs.ehu.es
10:56 a.m.
Am 05.02.2008 20:59, Allin Cottrell schrieb:
But this has a "preserve" option:
dataset clear --preserve
which has the effect that existing named matrices are not
destroyed.
Similarly, the commands "open" and "nulldata" have a --preserve
option: clear most stuff out, but keep matrices.
I guess this does not cover scalar variables, what about the new string
variables?
Or to put it differently: What's the rationale behind displaying scalars
in the list of variables, but matrices as items in the session view? And
where (if anywhere) are the strings and lists?
With respect to scalars I guess the reason is historical, but then I
would suggest a reform according to some (intuitive?) guideline.
thanks,
sven
2:39 p.m.
On Wed, 6 Feb 2008, Sven Schreiber wrote:
Am 05.02.2008 20:59, Allin Cottrell schrieb:
>
> But this has a "preserve" option:
>
> dataset clear --preserve
>
> which has the effect that existing named matrices are not destroyed.
>
> Similarly, the commands "open" and "nulldata" have a --preserve
option:
> clear most stuff out, but keep matrices.
I guess this does not cover scalar variables, what about the new string
variables?
Nothing but matrices, so far. But scalars and strings are worth
thinking about.
Or to put it differently: What's the rationale behind displaying
scalars in the list of variables, but matrices as items in the
session view? And where (if anywhere) are the strings and lists?
With respect to scalars I guess the reason is historical, but
then I would suggest a reform according to some (intuitive?)
guideline.
Yes, this should be sorted out at some point. However, there's
_some_ sense in the current ad hoc setup, in that it would be
silly to give scalars icons in the session view, not so silly to
do that with matrices, IMO.
There's no GUI representation of saved lists or strings. I can't
see any use for giving the latter such a representation, but one
could probably think of a use for the former.
Allin.
4:54 p.m.
Am 06.02.2008 20:39, Allin Cottrell schrieb:
On Wed, 6 Feb 2008, Sven Schreiber wrote:
> Am 05.02.2008 20:59, Allin Cottrell schrieb:
>
>> But this has a "preserve" option:
>>
>> dataset clear --preserve
>>
>> which has the effect that existing named matrices are not destroyed.
>>
>> Similarly, the commands "open" and "nulldata" have a
--preserve option:
>> clear most stuff out, but keep matrices.
> I guess this does not cover scalar variables, what about the new string
> variables?
Nothing but matrices, so far. But scalars and strings are worth
thinking about.
What about the rule: there are two object classes, one which covers data
series and everything else which is saved in the datafile (as opposed to
the session file), and the remaining stuff which gretl does not save in
a datafile. (Don't know how gretl currently treats or should treat
scalars and strings.) '--preserve' would apply to all objects in the
second class.
...
However, there's
_some_ sense in the current ad hoc setup, in that it would be
silly to give scalars icons in the session view, not so silly to
do that with matrices, IMO.
True
There's no GUI representation of saved lists or strings. I can't
see any use for giving the latter such a representation, but one
could probably think of a use for the former.
I agree; for example for the py4gretl functions it would have been nice
if it had been possible to define and/or check the existing lists
visually before calling the function package. (The list definition
dialog from within the function package is very nice, couldn't that be
promoted to a more broadly available dialog?)
cheers,
sven
6128
days inactive
6130
days old
4 comments
3 participants
participants (3)
-
Allin Cottrell -
Ignacio Diaz-Emparanza -
Sven Schreiber