[yt-dev] Milliparsecs

Sam Skillman samskillman at gmail.com
Mon Dec 2 13:22:53 PST 2013


-0

I'd rather we all just use Mpc, but I'll go along with it.


On Mon, Dec 2, 2013 at 12:53 PM, Nathan Goldbaum <nathan12343 at gmail.com>wrote:

> Here is the change:
>
>
> https://bitbucket.org/ngoldbaum/yt/commits/2e6d536ffa1976e4699093c4bb3b3bc4ade3f9da
>
> We'll definitely be leaving 'm' -> 'milli' alone.  FWIW, we already do
> this by mapping 'mpc' -> 'Mpc' in plot labels.
>
>
> On Mon, Dec 2, 2013 at 3:46 PM, Britton Smith <brittonsmith at gmail.com>wrote:
>
>> Ok, then I will put my anal personality (which would never agree to such
>> a thing) aside and say I'm cool with this.
>>
>>
>> On Mon, Dec 2, 2013 at 8:43 PM, Matthew Turk <matthewturk at gmail.com>wrote:
>>
>>> Hi Britton,
>>>
>>> This would be in the units refactor of yt-3.0, and would *only* apply
>>> to parsecs.  This would be the exclusive special case of m[some unit]
>>> meaning Mega.
>>>
>>> -Matt
>>>
>>> On Mon, Dec 2, 2013 at 3:41 PM, Britton Smith <brittonsmith at gmail.com>
>>> wrote:
>>> > Hi Matt,
>>> >
>>> > Where exactly is this?  Is this in yt-3.0, and if so, would this apply
>>> to
>>> > all uses of m as milli?  Is that is so, then my concern is for when yt
>>> > becomes more used by other domains that actually do have a valid use
>>> for
>>> > milli.
>>> >
>>> > Britton
>>> >
>>> >
>>> > On Mon, Dec 2, 2013 at 8:24 PM, Matthew Turk <matthewturk at gmail.com>
>>> wrote:
>>> >>
>>> >> Hi all,
>>> >>
>>> >> Nathan and I are working on some unit things.  One that came up is
>>> >> that it looked like the conversion to mpc was wrong.
>>> >>
>>> >> Turns out, it's not.  But what it's set up as is "mpc" for
>>> >> "milliparsecs" and "Mpc" for "Megaparsecs."  We'd like to get rid of
>>> >> any usage of milliparsecs, since I think the number of people who want
>>> >> to use that (globally) are probably between 0 and 0, and just make Mpc
>>> >> and mpc the same thing.
>>> >>
>>> >> If anybody objects, write back.  Silence will be taken as tacit
>>> agreement!
>>> >>
>>> >> -Matt
>>> >> _______________________________________________
>>> >> yt-dev mailing list
>>> >> yt-dev at lists.spacepope.org
>>> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>> >
>>> >
>>> >
>>> > _______________________________________________
>>> > yt-dev mailing list
>>> > yt-dev at lists.spacepope.org
>>> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>> >
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>>
>>
>> _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20131202/d053fa51/attachment.htm>


More information about the yt-dev mailing list