Hi, I noticed that between command and function is a major difference: dummify dList -> works with a list dummify(dList, NA) -> only one series accepted

In terms of the script output window I think what would be a nice-to-have is the option that as soon as output is added the window goes to the front. This is not always intended and could be annoying, but sometimes (especially if one likes the eval command) this would come in handy. Cheers Leon

With regard to dummify, I'm not sure that accepting a list argument is a great idea, since a (single) series argument already produces a list result. Producing a "list of lists" seems to me on the verge of being out of control.

Hi, I'm of the opinion that a "*" operator for interaction variables is a very useful means! A few weeks ago we discussed such possibilities in terms of MANOVA. This would be the solution to such problems of descriptive statistics and further analysis. What should be achieved? Well, I think list creation and usage in a model command like "dummify" now. Would be great if this functionality would be implemented! Have nice weekend Leon Am 30.12.2012 13:15, schrieb Riccardo (Jack) Lucchetti: > On Sun, 30 Dec 2012, Allin Cottrell wrote: > >> With regard to dummify, I'm not sure that accepting a list argument >> is a great idea, since a (single) series argument already produces a >> list result. Producing a "list of lists" seems to me on the verge of >> being out of control. > > Partially OT: I'm asking myself if we should go back to an idea that > we briefly considered when we introduced operators for lists, and > ended up being put on hold. > > The idea is to use the "*" operator for a specialised version of the > Cartesian product, commony known among applied economists as > "interaction" variables. To be more explicit: suppose you have two > lists, X and Y, with the only requirement that X should contain > discrete variables only. Then, the construct "X*Y" would perform what > is accomplished through the following script. > > <hansl> > open keane.gdt > list X = choice status > list Y = wage educ > > loop foreach j X --quiet > matrix v = values($j) > scalar n = rows(v) > loop foreach i Y --quiet > loop for k=1..n --quiet > xi = v[k] > sprintf vname "$i_$j_%d", xi > series @vname = ($j == xi)*$i > end loop > end loop > end loop > </hansl> > > Note that the dummify command/function would be a special case of > this for "Y=const". I have the feeling that people working with micro > data would love this. > > Thoughts? > > > ------------------------------------------------------- > Riccardo (Jack) Lucchetti > Dipartimento di Scienze Economiche e Sociali (DiSES) > > Università Politecnica delle Marche > (formerly known as Università di Ancona) > > r.lucchetti(a)univpm.it > http://www2.econ.univpm.it/servizi/hpp/lucchetti > ------------------------------------------------------- > > > _______________________________________________ > Gretl-users mailing list > Gretl-users(a)lists.wfu.edu > http://lists.wfu.edu/mailman/listinfo/gretl-users

On Thu, 14 Feb 2013, Pindar wrote: > Hi there, > > I'd like to ask what the interaction operator 'makes'? > > I was working on a function that generates new interaction series for > each step combination of factors. > This is working for a list of factors and generates bivariate > combinations as in A*B > I'm stuck with making it possible to generate A*B*C and so on. > This should be possible with a recursive function! > I think with a new gretl operato '*' the whole procedure would get > much easier to implement. > > I also encountered some bugs (at least on W8): > - having 'opened' a bundle and then using the '= null' command > gretl crashes > - 'smpl full' does 'sometimes' not work in functions - I think if > it's outside a loop. > - 'delete --type==' does not update the symbols window automatically > > Here is the code for the function as well (gonna be implemented in my > new multivariate statistic package). > Perhaps someone has an idea how to solve the sorting issue for more > than A*B. I've documented the new operator (warning: it's "^", not "*") in the CVS version of the manual not very long ago: in the A4 version (http://sourceforge.net/projects/gretl/files/manual/gretl-guide-a4.pdf/dow...) look for pages 91-92. Anyway, the following script should give you a good idea: <hansl> open mroz87.gdt --quiet # the coding below makes it so that # KIDS = 0 -> no kids # KIDS = 1 -> young kids only # KIDS = 2 -> young or older kids series KIDS = (KL6 > 0) + ((KL6 > 0) || (K618 > 0)) list D = CIT KIDS # interaction discrete variables list X = WE WA # variables to "split" list INTER = D ^ X smpl 1 6 print D X INTER -o </hansl> ------------------------------------------------------- Riccardo (Jack) Lucchetti Dipartimento di Scienze Economiche e Sociali (DiSES) Università Politecnica delle Marche (formerly known as Università di Ancona) r.lucchetti(a)univpm.it http://www2.econ.univpm.it/servizi/hpp/lucchetti -------------------------------------------------------

So now the interaction for bivariate combinations is MUCH shorter! Thanks for implementing the operator! In comparison to my function and the '^' operator result I noticed a slight difference: Is it intended that the value in 'grrr_grr_2' is '4' and not '1'?

<hansl> nulldata 10 matrix g1 = {1;1;1;1;1;1;2;2;2;2} matrix g2 = {1;1;1;1;1;1;1;1;2;2} matrix g3 = {1;1;2;2;2;3;3;3;4;4} series gr = g1 series grr = g2 series grrr = g3 delete --type=matrix # no instantly update of symbols list G1 = gr grr grrr list part1 = null list part2 = G1 list inter = null loop foreach i G1 -q part1 = G1.$i part2 -= G1.$i inter += part1^part2 endloop <hansl>

On Thu, 14 Feb 2013, Pindar wrote: > I also encountered some bugs (at least on W8) [...] Some of these I can replicate, some not. What version of gretl are you running (if a snapshot, what's the date?). Anyway, here's a run-through of the points you made: > - having 'opened' a bundle and then using the '= null' command gretl > crashes I can't replicate this. Here the following works fine: <hansl> bundle b b["foo"] = 6 print b b = null print b </hansl> > - 'smpl full' does 'sometimes' not work in functions - I think if it's > outside a loop. Inside a function, smpl --full only restores the sample range that was given by the caller. That is, it undoes any restriction on the sample range that was set inside the function, but not one set outside. The following illustrates the actual (and intended) behavior: <hansl> function void foo (series y) print y -o smpl +3 ; print y -o smpl full print y -o end function open data4-1 smpl 3 14 foo(price) </hansl> > - 'delete --type=' does not update the symbols window automatically Confirmed. There's an attempt at fixing that in CVS and today's snapshot. Should work for matrices and bundles. The scalars window may still need fixing. > - delete --type=series is not working. It's not supposed to work: "series" is not mentioned among the supported types for "delete --type=<typename>" in the help, and that is by design; you're not allowed to empty a dataset. But note that you can delete many series at once by using wildcards: <hansl> nulldata 20 loop i=1..10 series x$i = normal() endloop varlist delete x* varlist </hansl> > deleting a nonexisting lists leads to deleting the last > series of the dataset! Confirmed, and now fixed in CVS and snapshots. Allin Cottrell _______________________________________________ Gretl-users mailing list Gretl-users(a)lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-users

On Fri, 15 Feb 2013, Pindar wrote: > in terms of the bundle problem I was not concrete enough. > I'm using the current snapshot and still get a crash with: > > <hansl> > bundle b = null > b["foo"] = 1 > # open bundle via gui in symbol window > bundle b = null > # close bundle via gui -> crash > <hansl> OK, now I see what you mean. Fixed in CVS. > I have another question concerning loops: I want to use the @ functionality > for changing the looped through lists. > This is not working as expected. I need it for e.g. trivariate interaction: > > <hansl> > open chard.gdt > > loop for i=2..4 -q > string listName = "inter$i" > list @listName = null > endloop > > inter2 = 1 > inter3 = 3 4 > inter4 = 5 > > loop for i=2..4 -q > string listName = "inter$i" > loop foreach j @listName -q > print j > print "$j" > eval varname(@listName) > endloop > endloop > <hansl> This is a rather tricksy use of double string substitution: when the inner loop is set up is hard for gretl to know what "@listName" is, or will be. However, if we guess it ought to evaluate to a string that gives the name of a list, then things will go as you intend in this case. The following now works in CVS: <hansl> open data4-10.gdt list L1 = 1 list L2 = 3 4 list L3 = 5 loop i=1..3 -q string listName = "L$i" printf "i = %d: listName = '%s'\n", i, listName loop foreach j @listName -q printf " j = %d and dollar-j = '$j'\n", j endloop endloop </hansl> Allin Cottrell _______________________________________________ Gretl-users mailing list Gretl-users(a)lists.wfu.edu http://lists.wfu.edu/mailman/listinfo/gretl-users