On Mon, 22 Jan 2024, Sven Schreiber wrote:
I've stumbled over a certain behavior with panel data handling,
which could perhaps be a bug. However, it turned out that when I
closed and restarted gretl, the problem went away. It looks as if
it could be relevant that the panel datafile is a subset that was
saved as a gdt file as the result of earlier manipulation, and
continuing to work with the reduced dataset without starting a new
gretl session. My suspicion is that gretl wasn't able to fully and
cleanly switch over to the reduced dataset that was created and
retained.
I know that the problem is therefore quite subtle and probably not
directly reproducible. Nevertheless, let me show below what
happened in the console. Maybe it's still useful for something.
The dataset is monthly in the time dimension and recognized as
such by gretl, n=1..435 and t=2023:01..2023:12. (N*T = 5220)
Missings are present somewhere in most of the included variables.
[...]
Sven, I tried replicating what you describe but failed to replicate
the problem (not very surprising). Could you give us a little more
detail, please?
* What sort of manipulations preceded your saving of the panel
dataset to disk?
* When you saved the restricted dataset, did you use the "store"
command or the GUI? And if the latter, did you take the option (it's
offered in a dialog) of reducing the dataset in memory to that saved
to disk?
Allin