Bookmark and Share

Notice: On April 23, 2014, Statalist moved from an email list to a forum, based at statalist.org.


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: st: Why no error with -table- & trailing -if- ?


From   Steve Samuels <[email protected]>
To   [email protected]
Subject   Re: st: Why no error with -table- & trailing -if- ?
Date   Thu, 24 Oct 2013 18:01:22 -0400

Thanks.  I agree about the teaching. It's amusing that empty option
slots indicated by multiple commas are possible.

Steve

On Oct 24, 2013, at 9:12 AM, Nick Cox wrote:

This works for weights too:

. sysuse auto
(1978 Automobile Data)

. su mpg, detail, [w=length]
(analytic weights assumed)

                       Mileage (mpg)
-------------------------------------------------------------
     Percentiles      Smallest
1%           12             12
5%           14             12
10%           14             14       Obs                  74
25%           17             14       Sum of Wgt.       13907

50%           19                      Mean           20.75919
                       Largest       Std. Dev.      5.621854
75%           24             34
90%           28             35       Variance       31.60525
95%           31             35       Skewness        1.03329
99%           41             41       Kurtosis       4.274852

I have to say that I keep quiet about this feature when teaching Stata.
Nick
[email protected]


On 24 October 2013 13:52, Steve Samuels <[email protected]> wrote:
> 
> 
> Thanks, Nick. I managed to find that section myself. Sergiy, I now
> understand what you were describing: command-specific options can
> alternate with -if- and -in- qualifiers; a command-specific option must
> come first.  Also, the two qualifiers can appear together, as they
> can if written before the first comma, but only one instance of each is allowed.
> 
> So the following are both legal syntax:
> 
> . sum mpg, det, if foreign in 50/l, format
> . sum mpg, det, if foreign, format, in 50/l
> 
> 
> The Manual calls the insertion of the qualifiers a "return to the
> command line", what Sergiy called "command mode". Are there any other
> "command line" elements besides the qualifiers that can appear after a
> comma?
> 
> 
> Steve
> 
> On Oct 23, 2013, at 9:01 PM, Nick Cox wrote:
> 
> The perhaps surprising extended role of the comma is documented at [U] 11.1.7.
> 
> (http://www.stata.com/manuals13/u.pdf p.82)
> 
> 
> Nick
> [email protected]
> 
> 
> On 24 October 2013 00:46, Sergiy Radyakin <[email protected]> wrote:
>> On Wed, Oct 23, 2013 at 5:58 PM, Steve Samuels <[email protected]> wrote:
>>> 
>>> . sysuse auto, clear
>>> . table rep78, c(mean mpg), if turn<40
>> 
>> Because it is out of options already. Visualize it like this:
>> 
>> cmd , options,  more command, more options
>> 
>> Comma switches between the command and the options mode. So your
>> command is equivalent to:
>> table rep78 if turn<40, c(mean mpg)
>> 
>> Best, Sergiy Radyakin
>> 
>> 
>> 
>> 
>>> 
>>> 
>>> Steve
>>> [email protected]
>>> 
>>> 
>>> On Oct 21, 2013, at 9:35 PM, Sergiy Radyakin wrote:
>>> 
>>> Dear Dirk,
>>> 
>>> see if -savespss- and or saveto9.exe are able to help:
>>> http://www.radyakin.org/transfer/savespss/savespss.htm
>>> http://www.radyakin.org/transfer/saveto9/cs/index.htm
>>> 
>>> The first one is a Stata 10.0+ command (in Mata) that writes SPSS
>>> system files (*.sav) directly. The second one is a standalone utility
>>> to "downgrade" the version of the Stata dataset without Stata at all
>>> (neither Stata, nor SPSS, nor Stat/Transfer is necessary for it).
>>> 
>>> Best, Sergiy Radyakin
>>> 
>>> 
>>> 
>>> On Sat, Oct 19, 2013 at 4:41 PM, Dirk Enzmann
>>> <[email protected]> wrote:
>>>> Yes.
>>>> 
>>>> I cannot come up with hard numbers, but here are some impressions as to the
>>>> difficulties:
>>>> 
>>>> I already bought Stata from my private money (for use at my work!) - when I
>>>> bought it the first time (several years ago) my institution had no net
>>>> license of Stata; even after they decided to invest into a net license, I
>>>> regularary bought new versions because my instituion is too slow to invest
>>>> in updates (at the moment, the most recent version available is Stata 11!).
>>>> I would not starve if I had to buy StatTransfer on top of it, but I am
>>>> really hesitating because this I also had to pay subtracting from my salary
>>>> because this program does not belong to the software our institution bought
>>>> for use of their students or employees.
>>>> 
>>>> Until Stata 12 I could live comfortably without StatTransfer - I wrote an
>>>> SPSS script (SPSS2Stata.sbs) to translate SPSS files to Stata and a Stata
>>>> .ado (-dta2sav-) to move Stata files to SPSS. But the way to SPSS is blocked
>>>> now since Stata 13.
>>>> 
>>>> Luckily I have bought Stata 12 before, thus I can use it for moving files
>>>> from Stata 13 to SPSS - others, who are new to Stata since version 13 are
>>>> not so lucky.
>>>> 
>>>> I recently convinced colleagues in Finland to use Stata - but now they
>>>> recognize that they have to buy StatTransfer on top of it. Of course, this
>>>> is my fault, I should have told them before.
>>>> 
>>>> Some days ago there was a thread in the SPSS discussion list showing that
>>>> others experience this problem, as well (see:
>>>> http://spssx-discussion.1045642.n5.nabble.com/Stata-to-SPSS-conversion-td5722443.html
>>>> ).
>>>> 
>>>> Perhaps more important than money is the fact that even buying StatTranfer
>>>> does not help in all situations: It does not preserve labels of user missing
>>>> values (Stata's exended missing values) when transferring Stata data to SPSS
>>>> data (the other way round is also not without problems). To overcome this
>>>> problem, I wrote -dta2sav- (availabel on SSC). Unfortunately, if you don't
>>>> have an older version of Stata at your disposal (here, -uses13- can help),
>>>> you can't use it to transfer Stata 13 (format 117) files to SPSS.
>>>> 
>>>> Of course, you can blame SPSS for not updating their import routines (even
>>>> the maintenance of R's -foreign- package has been frozen for Stata formats
>>>> after 12, see http://cran.r-project.org/web/packages/foreign/foreign.pdf on
>>>> page 5), but this does not help users who want to use Stata in a context of
>>>> a majority (or important) colleagues still using SPSS.
>>>> 
>>>> Dirk
>>>> 
>>>> 
>>>> Sat, 19 Oct 2013 12:17:34 +0100, Nick Cox<[email protected]> wrote:
>>>>> 
>>>>> So, in summary, you appear to be saying that you know people who could
>>>>> afford Stata 13 but are reluctant to buy because they (a) would be in
>>>>> difficulty transferring their datasets to SPSS and (b) cannot afford
>>>>> StatTransfer as an extra purchase?
>>>>> 
>>>>> That's interesting. I have got to say that they are missing out on a
>>>>> great upgrade.
>>>>> 
>>>>> I just checked and a single user academic license [sic] of
>>>>> StatTransfer is USD 179.
>>>> 
>>>>> 
>>>>> 
>>>>> As I understand, Sergiy's add-ons could help them a lot.
>>>>> 
>>>>> StataCorp would, I think, be interested in hard evidence that they are
>>>> 
>>>>> losing out on sales because people really need a kind of "save to
>>>>> SPSS" command before they can decide to buy. I have no insight into
>>>>> how SPSS is managed.
>>>> 
>>>> --
>>>> ========================================
>>>> Dr. Dirk Enzmann
>>>> Institute of Criminal Sciences
>>>> Dept. of Criminology
>>>> Rothenbaumchaussee 33
>>>> D-20148 Hamburg
>>>> Germany
>>>> 
>>>> phone: +49-(0)40-42838.7498 (office)
>>>>     +49-(0)40-42838.4591 (Mrs Billon)
>>>> fax:   +49-(0)40-42838.2344
>>>> email: [email protected]
>>>> http://www2.jura.uni-hamburg.de/instkrim/kriminologie/Mitarbeiter/Enzmann/Enzmann.html
>>>> ========================================
>>>> *
>>>> *   For searches and help try:
>>>> *   http://www.stata.com/help.cgi?search
>>>> *   http://www.stata.com/support/faqs/resources/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/faqs/resources/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/faqs/resources/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/faqs/resources/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/faqs/resources/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/faqs/resources/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/faqs/resources/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/faqs/resources/statalist-faq/
*   http://www.ats.ucla.edu/stat/stata/


© Copyright 1996–2018 StataCorp LLC   |   Terms of use   |   Privacy   |   Contact us   |   Site index