Hi, perhaps we discussed this before: While it is possible in the GUI (menus) to define a dummy indicating the currently active sample, it doesn't seem directly possible to set the sample based on such a dummy. I had problems explaining to new users why that is. I know you can go to Sample/restrict by condition and then type something like mydum==1 in the text field. I also know how to do that in a script. But wouldn't it be more natural if in Sample/choose range there was a way to simply pick the dummy variable and use that automatically?

Am 17.04.2020 um 13:05 schrieb Riccardo (Jack) Lucchetti: > On Fri, 17 Apr 2020, Sven Schreiber wrote: > >> perhaps we discussed this before: While it is possible in the GUI >> (menus) to define a dummy indicating the currently active sample, it >> doesn't seem directly possible to set the sample based on such a dummy. >> I had problems explaining to new users why that is. >> >> I know you can go to Sample/restrict by condition and then type >> something like mydum==1 in the text field. I also know how to do that in >> a script. But wouldn't it be more natural if in Sample/choose range >> there was a way to simply pick the dummy variable and use that >> automatically? > > Uhm, is this a trick question? The dialog you get with "Restrict, > Based on Criterion" has a radio button that does exactly what you say. That would explain why I had déjà-vus about this topic. But unfortunately I don't have that button here. This is 2020a on Windows 10. I will try to cleanly install 2020b and see what happens.

Am 17.04.2020 um 13:30 schrieb Riccardo (Jack) Lucchetti: > On Fri, 17 Apr 2020, Sven Schreiber wrote: > >> >>> Uhm, is this a trick question? The dialog you get with "Restrict, >>> Based on Criterion" has a radio button that does exactly what you say. >> >> That would explain why I had déjà-vus about this topic. But >> unfortunately I don't have that button here. This is 2020a on Windows >> 10. I will try to cleanly install 2020b and see what happens. > > Aha! You only have that button if your currently open dataset contains > a dummy. Try this: Yes, your example works.  I think I found out the problem: - with bjg.gdt open, in the GUI choose shorter sample - Add/sample range dummy, don't change the setting (equal to active sample), choose name "d" - restore full sample - go to Sample/restrict based on criterion -> no radio button It seems the dummy isn't allowed to contain missing values. Wouldn't it make sense to treat missings as zeros in this context?

Am 17.04.20 um 21:47 schrieb Allin Cottrell: > On Fri, 17 Apr 2020, Sven Schreiber wrote: > >> Yes, your example works.  I think I found out the problem: >> >> - with bjg.gdt open, in the GUI choose shorter sample >> >> - Add/sample range dummy, don't change the setting (equal to active >> sample), choose name "d" >> >> - restore full sample >> >> - go to Sample/restrict based on criterion >> >> -> no radio button >> >> It seems the dummy isn't allowed to contain missing values. Wouldn't it >> make sense to treat missings as zeros in this context? > > I see your point, but my inclination here would be to revise the > behavior of "Add observations range dummy". I think this should be > exempt from the usual rule that we write values for newly generated > series only within the current sample range -- otherwise this dummy > becomes kinda useless. We should write zeros for observations outside > of the current sample, not NAs. > > Anyone see a reason why not? > Is there a scripting / hansl analogue of this action that would be affected?