<div class="gmail_quote"><div>Hi all,</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> * Host an online workshop / office hours<br></blockquote><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Another alternative Sam has suggested which I like is instead<br>
to host office hours in IRC or G+ or something with video.<br>
<br></blockquote><div><br></div><div>I think this could be pretty useful on something like a every few months timescale, or more frequent if they are found to be productive. If we combined G+ Hangouts (since nearly everyone has gmail) with a code sharing program like <a href="http://collabedit.com/">http://collabedit.com/</a> or <a href="http://codr.cc/">http://codr.cc/</a> we could have a developer or two hang out and be available to chat with new/old users about any issues. I think just publicizing that we'll be hanging out through the yt-users list a few days ahead of time would do the trick. Anyways, this is a pretty low maintenance option that would allow "face-to-face" interaction with new users.</div>
<div><br></div><div>As for the physical meeting, I think it would be great to have and advertise to not only the people who are already on the yt-users list but also to people on the teragrid/XSEDE that don't know that they should be interested in yt. </div>
<div><br></div><div>Sam</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
However, one of the big questions that has come up with respect to a<br>
physical workshop is: what would we talk about? I scribbled out a few<br>
items this morning that I think could fill a goodly amount of time,<br>
which I have included below. My feeling from talking to others is<br>
that for it to be useful, we would need both beginner and advanced<br>
topics. My list is at the bottom of this email -- after writing this<br>
out I kind of came around and felt like there is enough material to<br>
fill up a few sessions.<br>
<br>
Anyway, I'd like to solicit some thoughts on this. Pretty much it<br>
comes down to:<br>
<br>
1a) Physical (likely spring), virtual (anytime) or no workshop?<br>
1b) If Physical, where? (Specifically, which institutions or regions<br>
would you prefer, and could you volunteer your location?)<br>
2) What do you think of the pseudo-agenda below?<br>
<br>
One last item is that I was the most skeptical about the feasibility<br>
of a workshop, and I have been brought around by other developers --<br>
who have impressed upon me that not only could we do this, we really<br>
*ought* to do it. If not now, at some point in the future.<br>
<br>
Thanks everyone,<br>
<br>
-Matt<br>
<br>
* Agenda Ideas *<br>
<br>
= Using yt =<br>
<br>
- Introduction to yt -<br>
Jargon and terminology<br>
Installation<br>
How to start up<br>
How to write a script<br>
How to examine a simulation's characteristics<br>
Examining individual grids<br>
Slicing<br>
Projecting<br>
Command-line tool<br>
<br>
- Data handling in yt -<br>
How to think of data objects in yt<br>
What is a field? (also: my_plugins.py)<br>
Basics of select/instantiating a data object<br>
How to call and use a derived quantity<br>
What DQs and DOs are available?<br>
Phase plots (1-, 2-, 3-D)<br>
<br>
- Visualizing data -<br>
Projections, slices, and plot modifications<br>
Raw, stripped down plot objects<br>
Manually plotting data<br>
<br>
- Advanced data objects -<br>
Accessing attributes of data objects<br>
Cutting and subselecting data from objects<br>
Creating new data objects<br>
1D and 2D objects<br>
Creating fields<br>
Clump finding<br>
Finding points<br>
<br>
- Advanced visualization -<br>
Writing your own plot callback<br>
Fixed resolution buffers<br>
<br>
- Volume rendering -<br>
What is "Volume Rendering"?<br>
How to use the camera<br>
How to write a transfer function<br>
Making animations: camera paths and normalization<br>
"Photo-realistic"<br>
<br>
- Astrophysical Analysis -<br>
Halo finding<br>
Halo analysis / halo profiler<br>
Halo mass functions<br>
Spectral energy distribution<br>
Star particle analysis<br>
Absorption spectra<br>
<br>
- Large data analysis -<br>
How to run in parallel<br>
What kind of datasets work well with parallelism?<br>
Do's and don'ts of parallel analysis<br>
Distributing work<br>
<br>
- Time series analysis -<br>
Full simulation<br>
Analysis objects<br>
Multi-level Parallelism<br>
<br>
- Reason -<br>
How to use reason<br>
How does reason work<br>
Advanced features<br>
<br>
= Advanced yt + Developing yt =<br>
<br>
- Overview of the yt community -<br>
Communication channels<br>
Source control<br>
Testing<br>
Documentation<br>
People<br>
<br>
- Mercurial -<br>
What is version control?<br>
What is distributed version control?<br>
What's a DAG?<br>
<br>
- Contributing changes -<br>
How to commit, share, and notify<br>
What to expect when you contribute<br>
<br>
- The yt testing system -<br>
How to write a test<br>
How do tests get run?<br>
What does it mean to 'pass' a test?<br>
<br>
- How to write a code frontend -<br>
What does yt expect from a simulation output format?<br>
What is necessary / expected<br>
Simple prototyping<br>
How to construct the necessary source files<br>
<br>
- Fast code and Cython -<br>
What is Cython?<br>
How do I compile and run Cython code?<br>
How to speed it up<br>
<br>
- Writing parallel code -<br>
How does yt use parallelism?<br>
What routines are available for parallelism?<br>
How to debug parallel code<br>
<br>
- Interfacing with external code -<br>
Raw C api<br>
Exporting data objects<br>
Cython for easy API usage<br>
<br>
- yt internals -<br>
Parameter file storage and pickling<br>
kD-trees<br>
Idiomatic yt<br>
<div><div></div><div class="h5"><br>
On Mon, Aug 15, 2011 at 3:03 PM, Stephen Skory <<a href="mailto:s@skory.us">s@skory.us</a>> wrote:<br>
> Hi All,<br>
><br>
> I would be interested in a yt workshop. If it's combined with the Enzo<br>
> workshop this fall, it would reduce the number of plane tickets. If we<br>
> wait until spring, it would be even easier for me, as we are thinking<br>
> about hosting that edition of Enzo workshop here at CU (unless someone<br>
> else steps forward with more enthusiasm and money).<br>
><br>
><br>
> --<br>
> Stephen Skory<br>
> <a href="mailto:s@skory.us">s@skory.us</a><br>
> <a href="http://stephenskory.com/" target="_blank">http://stephenskory.com/</a><br>
> <a href="tel:510.621.3687" value="+15106213687">510.621.3687</a> (google voice)<br>
> _______________________________________________<br>
> Yt-dev mailing list<br>
> <a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
Yt-dev mailing list<br>
<a href="mailto:Yt-dev@lists.spacepope.org">Yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div><br>