Bookmark and Share

Notice: On March 31, it was announced that Statalist is moving from an email list to a forum. The old list will shut down on April 23, and its replacement, statalist.org is already up and running.


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

Re: Re: st: getting user-written commands presented at Stata user meetings?


From   Nick Cox <njcoxstata@gmail.com>
To   "statalist@hsphsun2.harvard.edu" <statalist@hsphsun2.harvard.edu>
Subject   Re: Re: st: getting user-written commands presented at Stata user meetings?
Date   Fri, 14 Jun 2013 15:34:01 +0100

I think this has already been answered, but the most common reasons I
can recall from those meetings I've been to are very simple:

0. Programs have already been posted, e.g. on SSC, or there's an
intent to post there soon.

1. The author considers the work as very much under development.

2. The code would not be of wider use because it is too closely linked
to stuff of some kind in the programmer's environment. do-files are an
obvious example.

3. The author wishes to publish in a more formal journal before releasing code.

Some of the habits of users' meetings go back to the first users'
meetings in London. In the early years the number of Stata programmers
was very small and many talks were on applications or were tutorial
talks. (One speaker omitted to mention Stata altogether, which was
felt to be going a bit far, so he's been banned for life.)
Nick
njcoxstata@gmail.com


On 14 June 2013 15:17, Ariel Linden, DrPH <ariel.linden@gmail.com> wrote:
> Thank you Nick and Sergiy.
>
> On the one hand, I can understand the issues you raise here with alluding to
> the proprietary nature of the programs, however, it seems odd to me that at
> a Stata users-meeting, the programs presented are not made available  (where
> everyone is a Stata user and would most likely want to use one or more of
> the programs presented).
>
> Ariel
>
> Date: Thu, 13 Jun 2013 19:14:06 +0100
> From: Nick Cox <njcoxstata@gmail.com>
> Subject: Re: st: getting user-written commands presented at Stata user
> meetings?
>
> Users' meetings are run locally and by many standards quite informally.
>
> The programme of each meeting is a series of talks given by Stata
> users and (often) StataCorp staff.
>
> Two linked patterns have been common for presented material:
>
> 1. Posting slides and sometimes software on www.stata.com
>
> 2. Equivalent posting on REPEC, usually organised by Kit Baum.
>
> I've never heard of any meeting insisting that code must be published.
> That would not be appropriate for many talks.
>
> In this case I was one of the organisers and can affirm that general
> arrangement.
> Nick
> njcoxstata@gmail.com
>
>
> On 13 June 2013 16:32, Ariel Linden, DrPH <ariel.linden@gmail.com> wrote:
>> I happened to come across this presentation that was given at the UK Stata
>> user meeting.
>>
>> www.timberlake.co.uk/common/pdf/stata-uk-12-ugm/uk12_dorn.pdf
>>
>> Interestingly enough, I cannot find the actual command -pscore2- that this
>> presentation describes (nor can I find the contact information for the
>> author). My questions are both general and specific:
>>
>> (1) General: is there an expectation that a command presented at a Stata
>> users meeting would be made available to the public? Similarly, why would
>> there be no contact information for the author? That is, unless they do
> not
>> want to be contacted.
>>
>> (2) Specific: How do I actually get hold of -pscore2-? I went through the
>> usual channels in Stata (findit) as well as a google search...
>>
>> It seems rather odd to me...
>>
>> Ariel
>
>
> *
> *   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–2014 StataCorp LP   |   Terms of use   |   Privacy   |   Contact us   |   Site index