Hi folks,
We have a set of projects on the website:
http://yt-project.org/extensions.html
I'd like to propose that we extend this a bit further and also allow
extensions to host their websites on our page as well. This would be
two things:
* They can either do this via submodules in the yt-project/website
repository, which would correspond to subdirectories or by including
their own subdirectory in the website repo.
* If there is affiliated data, it can be stored data in hub.yt and
referenced via AJAX calls (or manually listed)
I don't think this is a contentious thing, so unless I hear objections
I'll add the info to the YTEP and the skeleton extension repo.
-Matt

Hi folks,
Last week at SciPy, Nathan Goldbaum and Meagan Lang gave a talk about
the "demeshening" project. This is the project they're working on to
build out next-gen particle support in yt, based around removing the
octree indexing and adding in bitmap indexing, and in the process
getting a better representation of the particles.
Anyhow, the talk is online and is really quite good, so I wanted to
pass it along. It goes into some detail about what it means for
people using yt, as well as the underlying machinery.
https://www.youtube.com/watch?v=pkZgQIGac6I
-Matt

Hi all,
Would anyone be interested in helping out on Saturday or Sunday with the
SciPy sprint for yt? You would just need to be available on Slack to chat
and help out with new people. I was just told that 240 people signed up to
attend the sprints this year. This is also the first year we're on github,
so I expect that we will have more newcomers who are interested in helping
out.
If you're interested, let me know off-list so I can add your information to
the spreadsheet the sprint organizers are maintaining.
-Nathan

Hi all,
I tested yt with the release candidate and didn't run into any issues.
We're using very stable parts of the sympy API so I'm not expecting
breakage. That said, if anyone notices issues related to this please let me
know and I will fix ASAP.
-Nathan
---------- Forwarded message ----------
From: Aaron Meurer <asmeurer(a)gmail.com>
Date: Thu, Jul 6, 2017 at 3:15 PM
Subject: [sympy] SymPy 1.1 is released
To: "sympy(a)googlegroups.com" <sympy(a)googlegroups.com>
I'm happy to announce that SymPy 1.1 has been released. You can install it
with
pip install -U sympy
It also be available via conda soon.
This is a major release of SymPy, with many major changes since the
previous version, 1.0. The release notes are at
https://github.com/sympy/sympy/wiki/Release-Notes-for-1.1 (note, at
the time of this writing, these are still being updated).
Please report any bugs you find in our issue tracker
https://github.com/sympy/sympy/issues
Some highlights (if I am missing anything major, please let me know
and update the release notes page):
- Many improvements to code generation, including addition of
tensorflow (to lambdify), C++, llvm JIT, and Rust language support, as
well as the beginning of AST classes.
- Experimental support for SymEngine as a symbolic core in the
sympy.physics.mechanics module (set the environment variable
USE_SYMENGINE=1).
- A reworking of the internals of the matrices module.
- Several bug fixes for floating point numbers using higher than the
default precision.
In addition, several improvements from the 2016 Google Summer of Code
projects, including:
- A new holonomic submodule, for computing with holonomic functions
(Shubham Tibra's GSoC project).
- Improvements to the group theory module (Gaurav Dhingra's GSoC project).
- Improvements to the solvers and solveset (Shekhar Prasad Rajak and
Kshitij Saraogi's GSoC projects).
- Implementation of Singularity Functions to solve Beam Bending
problems (Sampad Kumar Saha's GSoC project).
- Improvements to the mechanics module (James Brandon Milam's GSoC project).
Thank you to everyone who contributed to this release. A full list of
people who contributed is at
https://github.com/sympy/sympy/wiki/Release-Notes-for-1.1#authors. A
total of 184 people contributed to this release. Of these, 143 people
contributed to SymPy for the first time for this release.
Aaron Meurer
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to sympy+unsubscribe(a)googlegroups.com.
To post to this group, send email to sympy(a)googlegroups.com.
Visit this group at https://groups.google.com/group/sympy.
To view this discussion on the web visit https://groups.google.com/d/
msgid/sympy/CAKgW%3D6K5xtb8KxnEzSVihoUZ7pBh3%2BnOi13N-EPA0WhzFgg7qg%40mail.
gmail.com.
For more options, visit https://groups.google.com/d/optout.

Hi yt developers,
I'm trying to produce 3D streamlines using the AMR data from FLASH following the yt-project tutorial http://yt-project.org/doc/visualizing/streamlines.html. However, the execution was very slow (in particular, at the 'Streamlines' call). The code didn't complete one single streamline after an hour.
Here's the excerpt of my code:
—————
c = ds.domain_center
streamlines = Streamlines(ds, c, 'velx', 'vely', 'velz', length=1.0*pc, get_magnitude=False)
streamlines.integrate_through_volume()
fig=plt.figure()
ax = Axes3D(fig)
for stream in streamlines.streamlines:
stream = stream[np.all(stream != 0.0, axis=1)]
ax.plot3D(stream[:,0], stream[:,1], stream[:,2], alpha=0.1)
plt.savefig('streamlines.png')
—————
I have two thoughts:
1. My FLASH file is quite large (~10GB). It may just be slow because of the large AMR grid size. Are there any ways to read only the velocities off the grid or only a subsection of the grid?
2. FLASH's octree data structure may be incompatible with the AMRKDTree construction (first step in streamlines creation). In the doc string of AMRKDTree, it says "Not applicable to particle or octree-based datasets.". If it's the case, I may have to find another way out.
Thank you very much for your time! Have a great weekend!
Best,
Benny

Hi Folks,
I submitted this PR earlier today:
https://github.com/yt-project/yt/pull/1476 <https://github.com/yt-project/yt/pull/1476>
which provides a wrapper to SlicePlot that removes the "axis" argument and plots 2D datasets only.
Since it’s a function, we probably ought to give it a function-like name (all-lowercase with underscores to separate words), as Nathan has suggested. Something like plot_2d.
Any other ideas for a name?
Best,
John