<div dir="ltr">I'm +0 on having mpc map to Mpc. I think this is a good situation where we could have a note in the docs about the case-sensitivity of units in the gotchas section of units or fields or some such.</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 2, 2013 at 2:32 PM, j s oishi <span dir="ltr"><<a href="mailto:jsoishi@gmail.com" target="_blank">jsoishi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Well, count me as a not terribly passionate -1. I think the idea that coding around the habits of certain subsets of users of yt has gotten us into trouble in the past, and I'm wary of doing it here. While this is certainly not a huge deal, I personally prefer that we be stricter about units standards. However, I totally understand that milliparsecs is not used by anyone. And of course, parsecs are not SI to begin with, so I suppose from a PURELY logical standpoint, we aren't necessarily bound by their prefix conventions. <span class="HOEnZb"><font color="#888888"><div>
<br></div><div>j</div></font></span></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="im">On Mon, Dec 2, 2013 at 4:22 PM, Sam Skillman <span dir="ltr"><<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>></span> wrote:<br>
</div><div><div class="h5"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">-0 <div><br></div><div>I'd rather we all just use Mpc, but I'll go along with it.</div>
</div><div>
<div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Dec 2, 2013 at 12:53 PM, Nathan Goldbaum <span dir="ltr"><<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Here is the change:<div><br></div><div><a href="https://bitbucket.org/ngoldbaum/yt/commits/2e6d536ffa1976e4699093c4bb3b3bc4ade3f9da" target="_blank">https://bitbucket.org/ngoldbaum/yt/commits/2e6d536ffa1976e4699093c4bb3b3bc4ade3f9da</a><br>
</div><div><br></div><div>We'll definitely be leaving 'm' -> 'milli' alone. FWIW, we already do this by mapping 'mpc' -> 'Mpc' in plot labels.</div></div><div><div>
<div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Dec 2, 2013 at 3:46 PM, Britton Smith <span dir="ltr"><<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Ok, then I will put my anal personality (which would never agree to such a thing) aside and say I'm cool with this.</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Mon, Dec 2, 2013 at 8:43 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Britton,<br>
<br>
This would be in the units refactor of yt-3.0, and would *only* apply<br>
to parsecs. This would be the exclusive special case of m[some unit]<br>
meaning Mega.<br>
<br>
-Matt<br>
<div><div><br>
On Mon, Dec 2, 2013 at 3:41 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>> wrote:<br>
> Hi Matt,<br>
><br>
> Where exactly is this? Is this in yt-3.0, and if so, would this apply to<br>
> all uses of m as milli? Is that is so, then my concern is for when yt<br>
> becomes more used by other domains that actually do have a valid use for<br>
> milli.<br>
><br>
> Britton<br>
><br>
><br>
> On Mon, Dec 2, 2013 at 8:24 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> Nathan and I are working on some unit things. One that came up is<br>
>> that it looked like the conversion to mpc was wrong.<br>
>><br>
>> Turns out, it's not. But what it's set up as is "mpc" for<br>
>> "milliparsecs" and "Mpc" for "Megaparsecs." We'd like to get rid of<br>
>> any usage of milliparsecs, since I think the number of people who want<br>
>> to use that (globally) are probably between 0 and 0, and just make Mpc<br>
>> and mpc the same thing.<br>
>><br>
>> If anybody objects, write back. Silence will be taken as tacit agreement!<br>
>><br>
>> -Matt<br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Cameron Hummels<div>Postdoctoral Researcher</div><div>Steward Observatory</div><div>University of Arizona</div><div><a href="http://chummels.org" target="_blank">http://chummels.org</a></div>
</div>