<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The latest development version of yt now has “unit systems”:<div class=""><br class=""></div><div class=""><a href="http://yt-project.org/docs/dev/analyzing/units/unit_systems.html" class="">http://yt-project.org/docs/dev/analyzing/units/unit_systems.html</a></div><div class=""><br class=""></div><div class="">But Nathan is correct—this doesn’t affect the Tesla unit per se—it should be fine. If we could get a script and a more specific error that you are seeing, that would help. </div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On May 24, 2016, at 12:30 PM, Huebl, Axel <<a href="mailto:a.huebl@hzdr.de" class="">a.huebl@hzdr.de</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi yt-devs,<br class=""><br class="">I am forwarding this conversation to the public list to keep it open for<br class="">others to join in and to build up a record that might help others.<br class=""><br class="">Our new student Fabian updated our frontend and implemented particle<br class="">readers. Unfortunately some details of the particle "fields" still cause<br class="">some bumps that we can not get our head around.<br class=""><br class="">We are now able to read fields and particles, even chunk-wise, and can<br class="">work with the data we read in python scripts via the all_data() method.<br class=""><br class="">Nevertheless, using the particle scatter plots such as yt.ParticlePlot<br class="">seems not to work. We have some problems with unions / the "all" group<br class="">and the fact that we have several particle species (e.g., "hot<br class="">electrons", "cold electrons", "helium ions", "nitrogen ions", etc.)<br class=""><br class="">Also since the last rebase: did someone recently change the unit system<br class="">in yt? T for "Tesla" seems not to be understood any more. Is there a<br class="">changelog somewhere available? Do we have to describe our data in cgs / mks?<br class=""><br class="">Would someone be interested for a quick heads up via e.g., skype /<br class="">web-rtc so we can ask specific questions?<br class=""><br class="">Fabian is around on Tuesdays and Fridays, something like early CA time,<br class="">and late GER time usually works great (e.g., 9pm-PDT / 6pm-CEST).<br class=""><br class="">Our current branch HEAD can be found here (->yt->frontends->openPMD):<br class=""> <a href="https://bitbucket.org/C0nsultant/openpmd/src?at=yt" class="">https://bitbucket.org/C0nsultant/openpmd/src?at=yt</a><br class=""><br class="">And an example script is attached.<br class=""><br class=""><br class="">Thanks a lot!<br class="">Axel<br class=""><span id="cid:3FD6775D-DE9A-4D40-8BA5-6AC988D93894"><read_openPMD.py></span>_______________________________________________<br class="">yt-dev mailing list<br class=""><a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org<br class=""></div></div></blockquote></div><br class=""></div></body></html>