Mailman 3 August 2015 - yt-dev

Issue #1066: Default origins for different geometries based on axis (yt_analysis/yt)
by Matthew Turk Aug. 19, 2015

Aug. 19, 2015

New issue 1066: Default origins for different geometries based on axis https://bitbucket.org/yt_analysis/yt/issues/1066/default-origins-for-differ… Matthew Turk: For some geometries, like cylindrical, there are natural origins for the plots one would want to use. For instance, if we are looking at a plot along R and z of a cylindrical dataset (i.e., slice along theta), we probably want "native" to be the default origin. Right now, this is not implemented, and in principle it should be … [View More]

1 0

yt website autodeployment
by Kacper Kowalik Aug. 14, 2015

Aug. 14, 2015

Hi All, in order to ease up website deployment after each commit to yt_analysis/website I've set up webhook that will do all the magic after each merge / push. If anyone is interested in details, the machinery consists of: 1) webhook for push that posts to http://hub.yt/webdeploy/ (configurable on bb) 2) simple webservice[1] that executes ssh to dickenson using custom key 3) following entry to .ssh/authorized_keys (at dickenson) command="sh /home/yt_analysis/.bin/deploy",no-port-… [View More]

2 1

Bookmarks now show up in the PR dropdown menu on bitbucket
by Nathan Goldbaum Aug. 13, 2015

Aug. 13, 2015

Hey all, With mercurial it's easy to get into a state where you have many heads, each one corresponding to a different open pull request on bitbucket. Up until now it's been sort of awful to use bitbucket with many heads, since the branch dropdown menu in the pull request interface only showed changeset hashes when a named branch has more the one heads. Now, thanks to Sean Farley at bitbucket, the PR dropdown menu looks like this: [image: Inline image 1] If you don't use bookmarks, you … [View More]

1 0

Issue #1065: documentation error in ortho_ray for projection=1 (yt_analysis/yt)
by Alex Hill Aug. 13, 2015

Aug. 13, 2015

New issue 1065: documentation error in ortho_ray for projection=1 https://bitbucket.org/yt_analysis/yt/issues/1065/documentation-error-in-ort… Alex Hill: The documentation of ortho_ray says, in describing coords, that "If you are casting along y, this will be (x,z)." In fact (empirically), the coord for casting along y is (z, x). Running Version = 3.1 Changeset = 4eb22c6d6fd9 stable

1 0

Older versions of the docs
by Kenza Arraki Aug. 12, 2015

Aug. 12, 2015

Does anyone have ideas on how we can encourage people to use the appropriate version of the docs? There are two issues that I see: - New users may not understand that there are different doc versions, so they may look at the wrong version for information - Google indexing previous doc versions Best, Kenza -- --------------- Kenza Arraki

6 6

Issue #1064: Cannot access projection_plot.plots[string].axes objects (yt_analysis/yt)
by ggoodwin52 Aug. 12, 2015

Aug. 12, 2015

New issue 1064: Cannot access projection_plot.plots[string].axes objects https://bitbucket.org/yt_analysis/yt/issues/1064/cannot-access-projection_p… ggoodwin52: In 3.2 we can no longer access and modify the plot axes. In 3.1 this could be done with the following code: ``` #!python p = yt.ProjectionPlot(ds,2,string,center=[cent,height,0],width=(wide,height),origin="native",data_source=cut,method='integrate',weight_field='temperature') ax = p.plots[string].axes ax.yaxis.set_ticks([0.00, 0.… [View More]

1 0

Issue #1063: New test failures using numpy 1.10 beta (yt_analysis/yt)
by Nathan Goldbaum Aug. 12, 2015

Aug. 12, 2015

New issue 1063: New test failures using numpy 1.10 beta https://bitbucket.org/yt_analysis/yt/issues/1063/new-test-failures-using-nu… Nathan Goldbaum: I'm seeing a number of new test failures when running the yt test suite under numpy 1.10b1. http://paste.yt-project.org/show/5812/ It looks like some are because things that have been deprecated for a long time are now raising a TypeError and others are due to changes in ndarray subclassing semantics (ugh).

1 0

Issue #1062: Loading SPH particle fields? (yt_analysis/yt)
by Adam Ginsburg Aug. 11, 2015

Aug. 11, 2015

New issue 1062: Loading SPH particle fields? https://bitbucket.org/yt_analysis/yt/issues/1062/loading-sph-particle-fields Adam Ginsburg: I'm trying to test out https://bitbucket.org/yt_analysis/yt/pull-requests/1688/wip-adding-support-… using some SPH data I have, but I don't have the fields loaded properly. I have a loader that mostly works, but I can't add the temperature field following this example: https://bitbucket.org/yt_analysis/yt/src/1f2ea0bf41846f243b50558c5eb9828bf0… the loader … [View More]

1 0

Weekly PR Triage Hangout
by Hilary Egan Aug. 11, 2015

Aug. 11, 2015

Here's the link to this week's hangout. Nice job to everyone who worked to tidy up loose ends last week for the 3.2 release! https://plus.google.com/b/107728486871834552760/events/c5d5rs0vgfrqfcuf8bcs… -Hilary

1 2

Issue #1061: Poor projection plot image quality in 3.2 (yt_analysis/yt)
by ggoodwin52 Aug. 10, 2015

Aug. 10, 2015

New issue 1061: Poor projection plot image quality in 3.2 https://bitbucket.org/yt_analysis/yt/issues/1061/poor-projection-plot-image… ggoodwin52: I recently started using 3.2 instead of 3.1 and noticed that the quality of the projection plot images decreased in the newest stable release of yt. I believe it is due to a lower resolution when rendering the plot in 3.2. Attached is a plot of the same temperature data, using both 3.1 and 3.2. You will notice that in the 3.2 plot the shocks (… [View More]green/blue temperature discontinuities) and the flame front (transition from red flame to yellow/green/blue gas) appear rough and pixelated, whereas they are nice and smooth in the 3.1 plot. This is not due to the computational cell size, as the cells along the flame and shocks are much smaller (3.333E-4 cm x 3.333E-4 cm) than the blocks you see in the plot image. Below is the code I used to generate these plots. The data I used is here: [http://use.yt/upload/a2346bb9](http://use.yt/upload/a2346bb9) The plot looks ok when using the default image size of 8, but when a larger image is used (I usually use 12) the quality is not as good. ``` #!python import yt import os import numpy as np import matplotlib.pyplot as plt import matplotlib.colors as mcolors from matplotlib.ticker import IndexLocator os.chdir("/lustre/ggoodwin/Ethylene_Air/plot_files_ethylene_br0.1_120cells_4nlev/det") colors1 = plt.cm.jet(np.linspace(0.0, 0.9, 1*2200)) #(0.2, 0.8, 25)) colors2 = plt.cm.hot_r(np.linspace(0.95, 1., 1*7716)) # 7716 colors3 = plt.cm.hot(np.linspace(0., 0.8, 1*14660)) # 14660 start at 2600K colors = np.vstack((colors1, colors2, colors3)) mymap = mcolors.LinearSegmentedColormap.from_list('my_colormap', colors, N=1*(2200+8578+13798)) ds = yt.load("plt000172380") ad = ds.all_data() products = ad.cut_region(['(obj["signed dist func"] < 0) & (obj["reactant mass frac"] < 0.5)']) # & (obj["y"] > 0.31)']) ploc = products.quantities.max_location("x") yH = ad.quantities.max_location("y") yy = ploc[0] - 0.5*yH[0] #+ 0.3*yH[0] yy2 = yy.value string = 'temperature' #schlieren cut = ad.cut_region(['(obj["signed dist func"] < 0)'])# & (obj["temperature"] >= 1000.)']) wide = 1.6 #1.6 height = 0.32 #0.32 if yy2 < wide/2.: cent = wide/2. else: cent = yy2 p = yt.ProjectionPlot(ds,2,string,center=[cent,height,0],width=(wide,height),origin="native",data_source=cut,method='integrate',weight_field='temperature')#,data_source=cut p.set_log(string,False) p.set_center((float(cent),float(height/2.))) p.set_minorticks(string,'off') p.set_zlim(string,300,6000) #1E-3,10 #p.set_zlim(string,1.E-3,50) p.plots[string].hide_colorbar() p.set_colorbar_label(string, '') #'Temperature [K]') p.set_cbar_minorticks(string,'off') p.set_cmap(field=string, cmap=mymap) #cmap='kamae_r') #'gray_r') p.set_figure_size('12') #12 p.set_font({'size':12}) p.save("/lustre/ggoodwin/Ethylene_Air/images/test") ``` [View Less]

1 0