Statalist


[Date Prev][Date Next][Thread Prev][Thread Next][Date index][Thread index]

Re: st: Re: saving memory local vs usual variable


From   "Eva Poen" <eva.poen@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: Re: saving memory local vs usual variable
Date   Fri, 3 Oct 2008 17:38:52 +0100

Not only -summarize-, but most statistical commands leave their
results behind. Just type -return list- after any command such as
-centile-, -ci-, -pwcorr-, -correlate-, -ttest-, -tabulate- etc. to
see what is there.

For estimation commands, it's -ereturn list- and results will be store
in e(). Same principle.

Note also the availability of scalars (-help scalar-) which can save
numbers in higher precision than local macros.

Eva


2008/10/3 Martin Weiss <martin.weiss1@gmx.de>:
> Anything that -su-, possibly with the -detail-, option throws up can be
> strored this way.
>
>                 r(N)
>             r(sum_w)
>              r(mean)
>               r(Var)
>                r(sd)
>          r(skewness)
>          r(kurtosis)
>               r(sum)
>               r(min)
>               r(max)
>                r(p1)
>                r(p5)
>               r(p10)
>               r(p25)
>               r(p50)
>               r(p75)
>               r(p90)
>               r(p95)
>               r(p99)
>
>
> Apart from that, also note commands like -collapse-...
>
> BTW, what is the second mode?
>
> HTH
> Martin
> _______________________
> ----- Original Message ----- From: "Ashim Kapoor" <ashimkapoor@gmail.com>
> To: <statalist@hsphsun2.harvard.edu>
> Sent: Friday, October 03, 2008 6:21 PM
> Subject: Re: st: Re: saving memory local vs usual variable
>
>
>> Yes I see that. Quite clever. BUT what if it is something which is NOT
>> generated by a summary statistic . Like say the 2nd mode  ( assuming a
>> variable has 2 modes). Can I directly store it into a local variable ?
>>
>> Thank you,
>> Ashim.
>>
>> On Fri, Oct 3, 2008 at 9:29 PM, Martin Weiss <martin.weiss1@gmx.de> wrote:
>>>
>>> As we said this morning:
>>>
>>> su age,mean
>>> loc lj=r(max)
>>>
>>> HTH
>>> Martin _______________________
>>> ----- Original Message ----- From: "Ashim Kapoor" <ashimkapoor@gmail.com>
>>> To: <statalist@hsphsun2.harvard.edu>
>>> Sent: Friday, October 03, 2008 5:54 PM
>>> Subject: st: saving memory local vs usual variable
>>>
>>>
>>>> Hello everyone,
>>>>
>>>> I have a question. Suppose I have a variable say - > age. Now I can do
>>>> egen j=max(age). Then I will have the max value of age in ONE
>>>> VARIABLE! Horrible waste of memory. I try to do local lj=max(age) and
>>>> that does not work. How can I conserve memory ? Is there something
>>>> basic which I have missed ?
>>>>
>>>> Thank you,
>>>> Ashim.
>>>>
>>>> PS : I do understand that I can do egen j = max (age ) and then say
>>>> local lj=j[1] and then -do drop j - but is there a better way ?
*
*   For searches and help try:
*   http://www.stata.com/help.cgi?search
*   http://www.stata.com/support/statalist/faq
*   http://www.ats.ucla.edu/stat/stata/



© Copyright 1996–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index