Hey all, I am trying to come up to speed on 2.0, and I'm getting this issue below. My question is, is this the way things are supposed to be? In particular, this is how it worked before, and how all of the docs & examples are written and posted on the website right now. Thanks! ------- $ iyt Welcome to yt! In [1]: pf = load("data0005") In [2]: h = parallelHF(pf) --------------------------------------------------------------------------- NameError Traceback (most recent call last) /home/sskory/yt/lib/python2.6/site-packages/yt-2.0dev-py2.6-linux-x86_64.egg/EGG-INFO/scripts/iyt in <module>() ----> 1 2 3 4 5 NameError: name 'parallelHF' is not defined _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Hi again,
I am trying to come up to speed on 2.0, and I'm getting this issue below. My question is, is this the way things are supposed to be? In particular, this is
how it worked before, and how all of the docs & examples are written and posted
on the website right now. Thanks!
Just to be clear, this is a real question. I didn't participate in any of the 2.0 conversion, so I really don't know what the new paradigm is. I would prefer if this hasn't been changed, but I don't know what's up. Thanks! _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Hi Stephen, My reading of your question is whether or not the parallelHF is included in the contents of "from yt.mods import *"; i.e., is it automatically imported and included in that name space. No, it currently isn't, but this was not (to my recollection) by design. The vast majority of users won't have access to the halo finder because the kD-tree installation is non-trivial. Forthon is not pip-installable and the kD-tree itself requires several steps to get installed (it doesn't work with distutils). So what was happening in the past was that most users were simply seeing a warning message for the code. (Additionally, on a more aesthetic note, it doesn't fit the naming convention: parallelHF.) However, those objections aside, my reading of the source is that in fact it *is* being imported because the mods.py file imports from analysis_modules.halo_finding.api, which pulls in parallelHF. It just doesn't get added to the local name space. It does get added to amods, as do all the analysis modules: from yt.mods import* amods.halo_finding.parallelHF If you think it should be directly imported into mods, then that's fine, you can go ahead and make that change. -Matt On Sat, Oct 2, 2010 at 3:32 PM, Stephen Skory <stephenskory@yahoo.com> wrote:
Hi again,
I am trying to come up to speed on 2.0, and I'm getting this issue below. My question is, is this the way things are supposed to be? In particular, this is
how it worked before, and how all of the docs & examples are written and posted
on the website right now. Thanks!
Just to be clear, this is a real question. I didn't participate in any of the 2.0 conversion, so I really don't know what the new paradigm is. I would prefer if this hasn't been changed, but I don't know what's up. Thanks!
_______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi Matt,
from yt.mods import* amods.halo_finding.parallelHF
If you think it should be directly imported into mods, then that's fine, you can go ahead and make that change.
I think that if we stick with everything following the "amods..." format, this is fine by me. With tab completion it won't be difficult for people to find what they need. The docs need to be updated, which I'll do for the ones I've written when I have time. _______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
Hi Stephen, Cool. I'm not sure I like "amods" (or "mods" to begin with) so if you have a better idea for "analysis modules" that isn't actually "analysis_modules" (binding to the name of a submodule is tricky) let me know. It's an object that will import on demand anything that lives under analysis_modules. -Matt On Mon, Oct 4, 2010 at 7:15 AM, Stephen Skory <stephenskory@yahoo.com> wrote:
Hi Matt,
from yt.mods import* amods.halo_finding.parallelHF
If you think it should be directly imported into mods, then that's fine, you can go ahead and make that change.
I think that if we stick with everything following the "amods..." format, this is fine by me. With tab completion it won't be difficult for people to find what they need. The docs need to be updated, which I'll do for the ones I've written when I have time.
_______________________________________________________ sskory@physics.ucsd.edu o__ Stephen Skory http://physics.ucsd.edu/~sskory/ _.>/ _Graduate Student ________________________________(_)_\(_)_______________
_______________________________________________ Yt-dev mailing list Yt-dev@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
participants (2)
-
Matthew Turk -
Stephen Skory