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: duplicated datetime variable differs from original datetime variable it was derived from


From   Nick Cox <[email protected]>
To   "[email protected]" <[email protected]>
Subject   Re: st: duplicated datetime variable differs from original datetime variable it was derived from
Date   Tue, 12 Nov 2013 16:59:38 +0000

Thanks for the closure here. Closure of threads is really helpful!

To convert seconds to milliseconds, multiply by 1000 (don't add).
Presumably you meant that....

On -format-: You're touching here on a widespread fallacy.  Changing
the format of a variable has precisely no effect on what is stored or
how it is stored. It does affect how something is displayed, but no
more. More detail at

http://www.stata-journal.com/article.html?article=dm0067

Nick
[email protected]


On 12 November 2013 14:18, Milena Przheska
<[email protected]> wrote:
> Dear Statalist members,
>
> Thank you all for taking the time to help me with this situation, your
> suggestions, lead me to the source of the problem (which I am
> embarrassed to admit) was a clumsy typing mistake.
>
> The thing was, I created a double variable time1 following Phil's
> advice, but then, when breaking ties between the values of the
> variable, instead of adding 1000 (the equivalent of 1 sec) I have
> added 100, which I think created the problem with the type of the
> variable, which was formatted as %9.0g. So I reformatted the variable
> to %12.0g and added 1000 for breaking ties, and now the model is
> running without errors (so far).
>
> I am really sorry for the confusion and once I again thank you all for
> your help.
>
*
*   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