Statalist


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

Re: st: saving memory local vs usual variable


From   "Sergiy Radyakin" <[email protected]>
To   [email protected]
Subject   Re: st: saving memory local vs usual variable
Date   Fri, 3 Oct 2008 14:14:51 -0400

Dear Ashim,

you may want to do one or another, and with some experience you will
feel what is right. Most or all of your questions are answered in
pretty much any Stata introduction guide. There is plenty of them in
the internet, e.g.
http://www.nyu.edu/its/statistics/Docs/Intro_stata5.pdf by Robert A.
Yaffee
or
http://www.folkesundhed.au.dk/uddannelse/software/besked.pdf by Svend Juul,
and many others written specifically for beginners.

The link to the UCLA website for Stata is attached to every message
sent to Statalist.
http://www.ats.ucla.edu/stat/stata/

If you want something more interactive, you may benefit from the Net
Courses conducted by Stata, Corp. The schedule and details are
available on their website:
http://www.stata.com/netcourse/

Regards, Sergiy Radyakin


On Fri, Oct 3, 2008 at 11:54 AM, Ashim Kapoor <[email protected]> wrote:
> 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/
>
*
*   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–2024 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   What's new   |   Site index