<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi all,<div><br></div><div>As part of the eternal journey that is making yt's plotting code as awesome as possible, we've endeavored to make the plotting code as flexible as it needs to be for quick use but simple enough that a use isn't overloaded by unnecessary or barely-used keyword arguments.</div><div><br></div><div>Right now there is a <a href="https://bitbucket.org/yt_analysis/yt/pull-request/496/plot-window-improvements-set_width/">pending PR</a> to rework some of the plotting routines, adding a couple of new features, and, per the subject of this e-mail, removing the max_level keyword from ProjectionPlot.</div><div><br></div><div>I could see how having max_level might be useful if projections are very slow for a user's dataset. However, she should be able to get the exact same result by explicitly constructing a projection data object and then creating a plot for it using projection.to_pw(). I also think in practice max_level isn't used very often since projections are quite fast, even on large datasets.</div><div><br></div><div>Am I incorrect in that assessment? Please let me know if you'd like to keep the max_level keyword around and I'll happily revert that part of the pull request.</div><div><br></div><div>Thanks for your help,</div><div><br></div><div>Nathan</div></body></html>