Statalist


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

Re: st: RE: Accessing command line parameters


From   "Sergiy Radyakin" <serjradyakin@gmail.com>
To   statalist@hsphsun2.harvard.edu
Subject   Re: st: RE: Accessing command line parameters
Date   Thu, 14 Feb 2008 14:22:30 -0500

Hello David,

I don't think that many people will be interested in the code here
(see earlier post by Nick Cox in this thread), but I have put the
compiled version and further instructions here:
ca.geocities.com/radyakin

This does not set the memory automatically for you, but it does give
you all the parameters, where you can decide which one is a filename
(by default it is the second one) and which strategy you want to
pursue in determining the memory size (see example by Austin Nichols
earlier in this thread).

Best regards,
   Sergiy Radyakin

PS: On this website you can also find a funny little program to teach
Stata to speak with a human voice (Windows only).




On 2/14/08, David Elliott <dcelliott@gmail.com> wrote:
> Sergiy, you do ask such interesting questions at times and like to
> "push the envelope"
>
> I have done a poor mans version of this with several Stata icons with
> different /k switches giving me different memory footprints.  I have a
> "small" Stata that I use for loading smaller tables while I have a
> large table in memory with my "main" Stata window.
>
> I will often start Stata with a known size for the table I want to
> open, but being able to auto configure would be a real boon.  Would
> you mind sharing the code you came up with as mentioned in your last
> post?
>
> DCE
> *
> *   For searches and help try:
> *   http://www.stata.com/support/faqs/res/findit.html
> *   http://www.stata.com/support/statalist/faq
> *   http://www.ats.ucla.edu/stat/stata/
>
*
*   For searches and help try:
*   http://www.stata.com/support/faqs/res/findit.html
*   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