st: RE: RE: how to use for* loops "noisily"?

["Martin Weiss" <martin.weiss1@gmx.de>]

<>

Also note -profiler-, btw.


HTH
Martin


-----Original Message-----
From: owner-statalist@hsphsun2.harvard.edu [mailto:owner-statalist@hsphsun2.harvard.edu] On Behalf Of David Radwin
Sent: Donnerstag, 29. Juli 2010 18:18
To: statalist@hsphsun2.harvard.edu
Subject: st: RE: how to use for* loops "noisily"?

László,

You might try using -set tracedepth 1- after -set trace on- to keep the 
output to a reasonable level within loops.

David
--
David Radwin
Research Associate
MPR Associates, Inc.
2150 Shattuck Ave., Suite 800
Berkeley, CA 94704
Phone: 510-849-4942
Fax: 510-849-0794

www.mprinc.com


> -----Original Message-----
> From: owner-statalist@hsphsun2.harvard.edu [mailto:owner-
> statalist@hsphsun2.harvard.edu] On Behalf Of László Sándor
> Sent: Thursday, July 29, 2010 9:06 AM
> To: statalist@hsphsun2.harvard.edu
> Subject: st: how to use for* loops "noisily"?
>
> Hi all,
>
> Sorry I could not google this down (or find in the manual): I am
> trying to use some efficient code, much like the advice of Kit Baum's
> books and Stata tips, but if I use loops (-foreach- or -forvalues-)
> for everything (cases, specification, restrictions etc.), I rarely see
> anything going on, only estimation results are coded to get
> posted/displayed in this case [by Stata], and the occasional (=
> omnipresent) error message.
>
> I experimented with turning -set trace on-, but it did more harm than
> good. Some clumsy bracketing into -noisily- chunks did not help
> either.
>
> Is there something to do if I'd like to run this do-file as a regular
> do-file for all commands, in or out of loops?
>
> Thanks,
>
> Laszlo


*
*   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/