YT development team:
We're happy to announce a new web-based GUI for yt called Reason
(version five!). It incorporates the full functionality of yt as well
as several additional features that should make using YT much more
efficient and interactive. In particular, new users and users working
on remote machines (e.g. kraken, ranger, pleaides, etc.) should find
this new GUI very useful as it allows one to interactively manipulate
and visualize non-local data.
Reason operates by creating a portable webserver on demand, which loads
a javascript page bridging to the yt/python interpreter. This page
provides an interpreter interface, with identical yt functionality,
where created images/plots are posted to the web interface. We're still
experimenting with how to provide access to this, but it includes the
ability to transfer and directly display images, display widgets for
interactive data exploration, and save and load scripts between runs.
To use Reason, you will need to have the ext-js and ext-slate-theme
packages, now included with the current install script. You can also
download these manually. Once installed, start it by simply running:
$ yt serve
If you are running locally and supply the -o option (yt serve -o), it
will open up a web browser automatically. There is also a help button
in the lower left of Reason with basic functionality explained. Keep in
mind that this is a BETA sequence (projection doesn't work yet), but
please check it out, play around with it, and report any bugs or desired
features missing from it.
--Cameron Hummels, Jeff Oishi, Britton Smith & Matt Turk
Hi all,
I've set up an IRC channel on irc.freenode.net. It's called #yt, and
I'm going to start sitting in it.
You can join using Adium (on OSX) or irssi or something on Linux.
I've also put up an IRC webchat frontend here:
http://yt.enzotools.org/irc.html
The Enzo workshop this week is using IRC and have found it (so far) to
be pretty productive. I think we could give this a shot and see if
it's worthwhile. If not, we can just let it be self-regulating. :)
-Matt
Hi Matt,
> >
> > In summary, for medium to very large sized clumps (in terms of number of
> cells), the treecode is showing it's usefulness. My tests are not complete,
> but the break even line with the standard opening angle (==approximation
> control) of 1.0, is about 100,000 cells. For example, a spherical clump with
> three levels and 120,000 cells takes 272 seconds with the O(N^2) method, 175
> seconds with the treecode, and has a 0.05% error.
>
> That's interesting. To be perfectly honest, I kind of expected it to
> perform a bit better. Any insight where the overhead comes from?
I'm not sure. I haven't timed individual steps of the code yet to see if something is unreasonably slow. Any useful tool recommendations are welcomed.
> It should be on by default. What is the performance difference, for a
> small/medium clump? 10%? 50%? Factor of 10?
It looks like it's no worse than a factor of two slower for opening_angle=1.0 at around 30,000 cells. I plan on making a figure showing this stuff soon.
> Very nice work! I have reviewed your changes and I think you should
> merge them. This will be a shining addition to the 2.1 release.
Thanks for the praise, I appreciate it.
> Could you post a script verifying that it works for clumps on the edge
> and in the center, to be added to the answer tests?
Sure, I can do that.
Stephen Skory
stephenskory(a)yahoo.com
http://stephenskory.com/
510.621.3687 (google voice)
Hi All,
Over the last two weeks I have been working on adding a treecode method as an option for calculating the gravitational boundedness of clumps. Now I can say that it's pretty much functional. I think there's at least one small optimization I can make before I am ready to merge & push it back into the mainline repo, but other than that I think things are pretty polished.
In summary, for medium to very large sized clumps (in terms of number of cells), the treecode is showing it's usefulness. My tests are not complete, but the break even line with the standard opening angle (==approximation control) of 1.0, is about 100,000 cells. For example, a spherical clump with three levels and 120,000 cells takes 272 seconds with the O(N^2) method, 175 seconds with the treecode, and has a 0.05% error.
One thought I have is whether or not the treecode should be a semi-automatic thing? As implied above, for small to medium clumps, the pure-C O(N^2) method is actually faster for several reasons. First, fewer data fields need to be generated. Second, small clumps will generally not benefit from the treecode method due to geometry, and the extra machinery of the octree slows it down, too. But for larger clumps, the treecode is clearly beneficial. The option to use the treecode would be a function of the number of cells in the clump. Thoughts?
As I've written things presently, the treecode will not help for unigrid datasets because the octree refinement levels match the dataset it's built to mirror. I think it should be possible to mock up fake levels in such a way that would allow the treecode method to work with unigrid datasets. In fact, I'm already doing something vaguely like this but only for the levels that actually exist in the dataset. My question is, do we think it is worth it? My impression is that clump finding is mostly done on AMR datasets, and this would add a bit of complexity. It's hard to say if it would have any advantage for AMR datasets.
I do need to do a bit of testing to make sure that my periodic changes work, but I don't foresee many problems with that.
I've already started adding some stuff to the docs on this, and I can finish them once the issues above are settled. Thanks for any thoughts you can share!
Stephen Skory
stephenskory(a)yahoo.com
http://stephenskory.com/
510.621.3687 (google voice)
Matt,
> Nope, not using it jsut now. I've found that for the most part, an
> -O0 compile of the cython stuff gives enough info and detail to handle
> it with standard gdb, since cython embeds the source lines.
What's your preferred way of ensuring a -O0 (or -g) compile with cython stuff?
Stephen Skory
stephenskory(a)yahoo.com
http://stephenskory.com/
510.621.3687 (google voice)
Hi Matt,
I took a look at the docs you coded up, and indeed there are some
interesting features with BB. In particular, I thought the `bbforks`
command sounded pretty cool - however, it appears I am missing the
lxml.html package, which is needed to get this to work:
---------------------------------------------------------------------------------------
[cmalone@xrb yt]$ hg bbforks
using 'ChrisMalone/yt-hg' as repo name
getting descendants list
abort: lxml.html is (currently) needed to run bbforks
---------------------------------------------------------------------------------------
I thought maybe it was perhaps a result of my BB repo not having any forks,
so I tried yours:
---------------------------------------------------------------------------------------
[cmalone@xrb yt]$ hg bbforks -n MatthewTurk/yt
getting descendants list
abort: lxml.html is (currently) needed to run bbforks
---------------------------------------------------------------------------------------
Is this missing in the install, or is it something on my end?
Chris
On Mar 23, 2011 10:31am, Matthew Turk <matthewturk(a)gmail.com> wrote:
> Hi John, and everyone else,
> Thanks! Plane flights are great for documentation (writing docs
> doesn't have to hit the disk or grind the processor) so I started
> writing up what it does:
> http://hg.enzotools.org/yt-doc/changeset/e8f532648a50
> I also went ahead, with the couple votes, and pushed it to the main
> repository.
> Thanks everybody,
> Matt
> On Wed, Mar 23, 2011 at 9:07 AM, John Wise jwise(a)astro.princeton.edu>
> wrote:
> > Hi Matt,
> >
> > I'ma little late to the game since other less interesting things took
> priority. I tested out the bootstrap script, and everything went
> smoothly! I voted "0" before because I didn't really see the bigger
> picture of what you were talking about, but now I'm convinced.
> >
> > +1.
> >
> > John
> >
> > On 21 Mar 2011, at 16:14, Matthew Turk wrote:
> >
> >> Hi Chris,
> >>
> >> Ah, yes, you're totally right. I'll add an inventory-regeneration
> >> command, which looks at the current manifest of the repo and then
> >> regenerates inventory.json to match it. (This allows you to, for
> >> instance, remove pastes from the current display, add supplemental
> >> images, etc etc.) Pushing, like you say, also fixes the display on
> >> the website.
> >>
> >> -Matt
> >>
> >> On Mon, Mar 21, 2011 at 1:11 PM, chris.m.malone(a)gmail.com> wrote:
> >>> I should chime in and say that my pasteboard page was not setup after
> the
> >>> bootstrapp'ing - the page just 404'ed. To fix this I just did a test
> commit
> >>> to the pasteboard
> >>>
> >>> yt pasteboard --desc="This is just a test" test.py
> >>>
> >>> and it worked fine. So, it _is_ set up with BB, as far as I can tell,
> but
> >>> the page just shows up as 404 until something is checked in, or
> following
> >>> Briton's elegant solution of just doing a 'hg push'
> >>>
> >>> Chris
> >>> On Mar 21, 2011 4:03pm, Britton Smith brittonsmith(a)gmail.com> wrote:
> >>>> I had a similar experience to Chris's. I gave the script my bitbucket
> >>>> username, but on the first try it wanted to use my system username,
> which is
> >>>> also not the same. Just like for Chris, it got it right the second
> time.
> >>>>
> >>>>
> >>>> As one of original nay-sayers on this, I have to say I liked
> everything
> >>>> about how this worked. I especially think the pasteboard is really
> great.
> >>>> The one thing that wasn't very clear to me was that I had to do
> an 'hg push'
> >>>> from within my pasteboard repo to get the page set up on bitbucket.
> Could a
> >>>> note of this be made in the script after this step is done?
> >>>>
> >>>>
> >>>> Since I'm wrong so often, it's quite easy for me to admit that I was
> wrong
> >>>> about this one.
> >>>>
> >>>> Nice job, Matt.
> >>>>
> >>>> Britton
> >>>>
> >>>> On Mon, Mar 21, 2011 at 2:49 PM, Chris Malone
> chris.m.malone(a)gmail.com>
> >>>> wrote:
> >>>>
> >>>> Hi Matt,
> >>>>
> >>>> I pulled from your repo and ran the
> >>>>
> >>>> yt bootstrap_dev
> >>>>
> >>>> method. Everything was going fine - it checked out yt-supplemental,
> >>>> looked at my .hgrc and added my BB username, etc - until it wanted
> to set up
> >>>> my pasteboard. It seems like when it made the hgbb._bb_apicall, it
> used my
> >>>> system user name, which is different from my BB username:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> -------------------------------------------------------------------------------------------------------------------------------------------------
> >>>> I am now going to create the repository:
> >>>> chrismalone.bitbucket.org
> >>>>
> >>>>
> >>>> on BitBucket.org. This will set up the domain
> >>>> http://chrismalone.bitbucket.org
> >>>> which will point to the current contents of the repo.
> >>>>
> >>>> Press enter to go on, Ctrl-C to exit.
> >>>>
> >>>>
> >>>> using system user 'cmalone' as usernamehttp authorization required
> >>>> realm: None
> >>>> user: cmalone
> >>>> password:
> >>>>
> >>>>
> -------------------------------------------------------------------------------------------------------------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>> Obviously this failed; however, when I ran this a second time it
> picked up
> >>>> my correct BB username:
> >>>>
> >>>>
> >>>>
> -------------------------------------------------------------------------------------------------------------------------------------------------
> >>>>
> >>>>
> >>>> I am now going to create the repository:
> >>>> chrismalone.bitbucket.org
> >>>> on BitBucket.org. This will set up the domain
> >>>> http://chrismalone.bitbucket.org
> >>>>
> >>>>
> >>>> which will point to the current contents of the repo.
> >>>>
> >>>> Press enter to go on, Ctrl-C to exit.
> >>>> http authorization required
> >>>> realm: None
> >>>> user: ChrisMalone
> >>>> password:
> >>>>
> -------------------------------------------------------------------------------------------------------------------------------------------------
> >>>>
> >>>>
> >>>>
> >>>> and then it worked fine. I can now use the pasteboard facilities,
> which
> >>>> are pretty cool!
> >>>>
> >>>> I think for the bootstrap utility to be a bit more user-friendly, you
> >>>> might want to add a bit more description about why the user cares
> about the
> >>>> various components that are about to be installed For example, the
> user
> >>>> probably doesn't know that the yt-supplemental repo is where all the
> hgbb or
> >>>> pasteboard stuff is contained or why they should want a BB account
> if they
> >>>> don't have one already. This might be too much information to have
> in the
> >>>> bootstrap script itself, so perhaps provide a link to a page where
> these
> >>>> things are mentioned.
> >>>>
> >>>>
> >>>>
> >>>> Anyhow, aside from the above (minor) points, I really like the
> bootstrap
> >>>> utility. You've gone out of your way to make sure nothing was done
> without
> >>>> the user's permission.
> >>>>
> >>>> +1
> >>>>
> >>>>
> >>>> Chris
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> On Mon, Mar 21, 2011 at 12:34 AM, Matthew Turk matthewturk(a)gmail.com>
> >>>> wrote:
> >>>>
> >>>>
> >>>> Hi all,
> >>>>
> >>>>
> >>>>
> >>>> Last week we had a conversation about a bootstrap script, where the
> >>>>
> >>>> feel of the room was either lukewarm or positive. Mostly people
> >>>>
> >>>> seemed to think it was ill-motivated or would take too many
> liberties.
> >>>>
> >>>> Over the last week, in the evenings etc I've created a bootstrap
> >>>>
> >>>> script for development, which overall I think is pretty
> >>>>
> >>>> well-motivated. The script accomplishes the following things, each of
> >>>>
> >>>> which requests for confirmation before going on. It uses a modified
> >>>>
> >>>> iniparse library so that any modifications to any ini files are made
> >>>>
> >>>> in a non-destructive manner. It accomplishes these tasks:
> >>>>
> >>>>
> >>>>
> >>>> 1) Ensure username is set up in ~/.hgrc
> >>>>
> >>>> 2) Ensure that the cedit and hgbb are enabled
> >>>>
> >>>> 3) Asks for and if needed creates a username on BitBucket
> >>>>
> >>>> 4) Sets up hgbb
> >>>>
> >>>> 5) Creates a pasteboard repository
> >>>>
> >>>>
> >>>>
> >>>> The diff is here:
> >>>>
> >>>>
> >>>>
> >>>> https://bitbucket.org/yt_analysis/yt/compare/MatthewTurk/yt..default
> >>>>
> >>>>
> >>>>
> >>>> You can pull from my repo:
> >>>>
> >>>>
> >>>>
> >>>> hg pull https://bitbucket.org/MatthewTurk/yt/
> >>>>
> >>>>
> >>>>
> >>>> (But note the comment below about yt-supplemental)
> >>>>
> >>>>
> >>>>
> >>>> There are a couple things in this:
> >>>>
> >>>>
> >>>>
> >>>> * I wrote up something called a "pasteboard" this last week for more
> >>>>
> >>>> permanent mini-pastes of info. This uses mercurial to create/destroy
> >>>>
> >>>> items in it. You can see some examples here:
> >>>>
> >>>>
> >>>>
> >>>> http://matthewturk.bitbucket.org/
> >>>>
> >>>> http://jsoishi.bitbucket.org/
> >>>>
> >>>> http://samskillman.bitbucket.org/
> >>>>
> >>>>
> >>>>
> >>>> This was born out of the SFLC thing that happened on the mailing
> list,
> >>>>
> >>>> when Sam emailed his script. I thought, wouldn't it be nice if we
> >>>>
> >>>> were older, and we had a pasteboard that was persistent, with
> >>>>
> >>>> descriptions, which we could programmatically upload/download from.
> >>>>
> >>>> This adds the new commands:
> >>>>
> >>>>
> >>>>
> >>>> yt pasteboard --desc="Something" some_file.py
> >>>>
> >>>> yt pastegrab PASTE_ID USERNAME
> >>>>
> >>>>
> >>>>
> >>>> This automatically tosses it up. You get embed codes and some
> >>>>
> >>>> highlights, but it's just easier to keep these things around than the
> >>>>
> >>>> pastebin.
> >>>>
> >>>>
> >>>>
> >>>> * The idea of enabling hgbb, cedit and ensuring a bitbucket user is
> >>>>
> >>>> because I am of the opinion we should make it easier to fork the
> >>>>
> >>>> repository to make changes. If those three are enabled, I believe a
> >>>>
> >>>> command-line forking, editing of sources and so on, are all within
> our
> >>>>
> >>>> reach.
> >>>>
> >>>>
> >>>>
> >>>> * This bootstrap script requires that the yt-supplemental repo be
> >>>>
> >>>> checked out in ${YT_DEST}/src/ . This repo is actually kind of cool,
> >>>>
> >>>> in that it is a subrepo setup, and it pulls in a couple external
> >>>>
> >>>> libraries that we can maintain. Right now it grabs the docs, the
> >>>>
> >>>> cookbook, and the extensions mentioned above. This repo is now pulled
> >>>>
> >>>> in the current install_script.sh.
> >>>>
> >>>>
> >>>>
> >>>> Anyway, I am submitting this to the list to get some review. There
> >>>>
> >>>> may be errors, but I have tested it quite a bit. It also informs the
> >>>>
> >>>> user of what it's about to do and requires the user hit enter. At one
> >>>>
> >>>> point it even asks for a yes or no.
> >>>>
> >>>>
> >>>>
> >>>> The reason I am interested in this is that I think the idea of
> >>>>
> >>>> bootstrapping people into a development environment is, generally, a
> >>>>
> >>>> good idea. Particularly because some things -- like the pasteboard,
> >>>>
> >>>> like forking, like contributing changes -- should be made really easy
> >>>>
> >>>> and have the potential for a very high payoff. I hope I've motivated
> >>>>
> >>>> things a bit better.
> >>>>
> >>>>
> >>>>
> >>>> I was hoping that before I merged it I could get someone else to read
> >>>>
> >>>> it over, maybe a couple people even to test it, and to get a good
> feel
> >>>>
> >>>> for whether this is worthwhile or whether I should pull these changes
> >>>>
> >>>> and just ignore the idea. What do people think?
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>>
> >>>>
> >>>>
> >>>> Matt
> >>>>
> >>>> _______________________________________________
> >>>>
> >>>> Yt-dev mailing list
> >>>>
> >>>> Yt-dev(a)lists.spacepope.org
> >>>>
> >>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>>
> >>>> Yt-dev mailing list
> >>>>
> >>>> Yt-dev(a)lists.spacepope.org
> >>>>
> >>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>> _______________________________________________
> >>> Yt-dev mailing list
> >>> Yt-dev(a)lists.spacepope.org
> >>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >>>
> >>>
> >> _______________________________________________
> >> Yt-dev mailing list
> >> Yt-dev(a)lists.spacepope.org
> >> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >
> > _______________________________________________
> > Yt-dev mailing list
> > Yt-dev(a)lists.spacepope.org
> > http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> >
> _______________________________________________
> Yt-dev mailing list
> Yt-dev(a)lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
I should chime in and say that my pasteboard page was not setup after the
bootstrapp'ing - the page just 404'ed. To fix this I just did a test commit
to the pasteboard
yt pasteboard --desc="This is just a test" test.py
and it worked fine. So, it _is_ set up with BB, as far as I can tell, but
the page just shows up as 404 until something is checked in, or following
Briton's elegant solution of just doing a 'hg push'
Chris
On Mar 21, 2011 4:03pm, Britton Smith <brittonsmith(a)gmail.com> wrote:
> I had a similar experience to Chris's. I gave the script my bitbucket
> username, but on the first try it wanted to use my system username, which
> is also not the same. Just like for Chris, it got it right the second
> time.
> As one of original nay-sayers on this, I have to say I liked everything
> about how this worked. I especially think the pasteboard is really great.
> The one thing that wasn't very clear to me was that I had to do an 'hg
> push' from within my pasteboard repo to get the page set up on bitbucket.
> Could a note of this be made in the script after this step is done?
> Since I'm wrong so often, it's quite easy for me to admit that I was
> wrong about this one.
> Nice job, Matt.
> Britton
> On Mon, Mar 21, 2011 at 2:49 PM, Chris Malone chris.m.malone(a)gmail.com>
> wrote:
> Hi Matt,
> I pulled from your repo and ran the
> yt bootstrap_dev
> method. Everything was going fine - it checked out yt-supplemental,
> looked at my .hgrc and added my BB username, etc - until it wanted to set
> up my pasteboard. It seems like when it made the hgbb._bb_apicall, it
> used my system user name, which is different from my BB username:
> -------------------------------------------------------------------------------------------------------------------------------------------------
> I am now going to create the repository:
> chrismalone.bitbucket.org
> on BitBucket.org. This will set up the domain
> http://chrismalone.bitbucket.org
> which will point to the current contents of the repo.
> Press enter to go on, Ctrl-C to exit.
> using system user 'cmalone' as usernamehttp authorization required
> realm: None
> user: cmalone
> password:
> -------------------------------------------------------------------------------------------------------------------------------------------------
> Obviously this failed; however, when I ran this a second time it picked
> up my correct BB username:
> -------------------------------------------------------------------------------------------------------------------------------------------------
> I am now going to create the repository:
> chrismalone.bitbucket.org
> on BitBucket.org. This will set up the domain
> http://chrismalone.bitbucket.org
> which will point to the current contents of the repo.
> Press enter to go on, Ctrl-C to exit.
> http authorization required
> realm: None
> user: ChrisMalone
> password:
> -------------------------------------------------------------------------------------------------------------------------------------------------
> and then it worked fine. I can now use the pasteboard facilities, which
> are pretty cool!
> I think for the bootstrap utility to be a bit more user-friendly, you
> might want to add a bit more description about why the user cares about
> the various components that are about to be installed For example, the
> user probably doesn't know that the yt-supplemental repo is where all the
> hgbb or pasteboard stuff is contained or why they should want a BB
> account if they don't have one already. This might be too much
> information to have in the bootstrap script itself, so perhaps provide a
> link to a page where these things are mentioned.
> Anyhow, aside from the above (minor) points, I really like the bootstrap
> utility. You've gone out of your way to make sure nothing was done
> without the user's permission.
> +1
> Chris
> On Mon, Mar 21, 2011 at 12:34 AM, Matthew Turk matthewturk(a)gmail.com>
> wrote:
> Hi all,
> Last week we had a conversation about a bootstrap script, where the
> feel of the room was either lukewarm or positive. Mostly people
> seemed to think it was ill-motivated or would take too many liberties.
> Over the last week, in the evenings etc I've created a bootstrap
> script for development, which overall I think is pretty
> well-motivated. The script accomplishes the following things, each of
> which requests for confirmation before going on. It uses a modified
> iniparse library so that any modifications to any ini files are made
> in a non-destructive manner. It accomplishes these tasks:
> 1) Ensure username is set up in ~/.hgrc
> 2) Ensure that the cedit and hgbb are enabled
> 3) Asks for and if needed creates a username on BitBucket
> 4) Sets up hgbb
> 5) Creates a pasteboard repository
> The diff is here:
> https://bitbucket.org/yt_analysis/yt/compare/MatthewTurk/yt..default
> You can pull from my repo:
> hg pull https://bitbucket.org/MatthewTurk/yt/
> (But note the comment below about yt-supplemental)
> There are a couple things in this:
> * I wrote up something called a "pasteboard" this last week for more
> permanent mini-pastes of info. This uses mercurial to create/destroy
> items in it. You can see some examples here:
> http://matthewturk.bitbucket.org/
> http://jsoishi.bitbucket.org/
> http://samskillman.bitbucket.org/
> This was born out of the SFLC thing that happened on the mailing list,
> when Sam emailed his script. I thought, wouldn't it be nice if we
> were older, and we had a pasteboard that was persistent, with
> descriptions, which we could programmatically upload/download from.
> This adds the new commands:
> yt pasteboard --desc="Something" some_file.py
> yt pastegrab PASTE_ID USERNAME
> This automatically tosses it up. You get embed codes and some
> highlights, but it's just easier to keep these things around than the
> pastebin.
> * The idea of enabling hgbb, cedit and ensuring a bitbucket user is
> because I am of the opinion we should make it easier to fork the
> repository to make changes. If those three are enabled, I believe a
> command-line forking, editing of sources and so on, are all within our
> reach.
> * This bootstrap script requires that the yt-supplemental repo be
> checked out in ${YT_DEST}/src/ . This repo is actually kind of cool,
> in that it is a subrepo setup, and it pulls in a couple external
> libraries that we can maintain. Right now it grabs the docs, the
> cookbook, and the extensions mentioned above. This repo is now pulled
> in the current install_script.sh.
> Anyway, I am submitting this to the list to get some review. There
> may be errors, but I have tested it quite a bit. It also informs the
> user of what it's about to do and requires the user hit enter. At one
> point it even asks for a yes or no.
> The reason I am interested in this is that I think the idea of
> bootstrapping people into a development environment is, generally, a
> good idea. Particularly because some things -- like the pasteboard,
> like forking, like contributing changes -- should be made really easy
> and have the potential for a very high payoff. I hope I've motivated
> things a bit better.
> I was hoping that before I merged it I could get someone else to read
> it over, maybe a couple people even to test it, and to get a good feel
> for whether this is worthwhile or whether I should pull these changes
> and just ignore the idea. What do people think?
> Thanks,
> Matt
> _______________________________________________
> Yt-dev mailing list
> Yt-dev(a)lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
> _______________________________________________
> Yt-dev mailing list
> Yt-dev(a)lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
Hi All,
We'd like some feedback on your use and your opinions about the future
of yt. It's really short, and no questions are mandatory, so feel free
to fill in as many or as few as you'd like. Please visit
https://spreadsheets.google.com/viewform?formkey=dGlFazdOcUtFbHJLVU80a2NGM3…
and answer away.
The last user survey was really useful for us to help make yt-2.0 what
it was. The future of yt is looking really bright, and we'd like to
ensure it is as useful as we can make it. If you'd like to get
involved at any point in the development process, feel free to email
yt-dev, or any member of the dev team individually.
Thanks, and we look forward to hearing from you!
Jeff
Hi all,
Last week we had a conversation about a bootstrap script, where the
feel of the room was either lukewarm or positive. Mostly people
seemed to think it was ill-motivated or would take too many liberties.
Over the last week, in the evenings etc I've created a bootstrap
script for development, which overall I think is pretty
well-motivated. The script accomplishes the following things, each of
which requests for confirmation before going on. It uses a modified
iniparse library so that any modifications to any ini files are made
in a non-destructive manner. It accomplishes these tasks:
1) Ensure username is set up in ~/.hgrc
2) Ensure that the cedit and hgbb are enabled
3) Asks for and if needed creates a username on BitBucket
4) Sets up hgbb
5) Creates a pasteboard repository
The diff is here:
https://bitbucket.org/yt_analysis/yt/compare/MatthewTurk/yt..default
You can pull from my repo:
hg pull https://bitbucket.org/MatthewTurk/yt/
(But note the comment below about yt-supplemental)
There are a couple things in this:
* I wrote up something called a "pasteboard" this last week for more
permanent mini-pastes of info. This uses mercurial to create/destroy
items in it. You can see some examples here:
http://matthewturk.bitbucket.org/http://jsoishi.bitbucket.org/http://samskillman.bitbucket.org/
This was born out of the SFLC thing that happened on the mailing list,
when Sam emailed his script. I thought, wouldn't it be nice if we
were older, and we had a pasteboard that was persistent, with
descriptions, which we could programmatically upload/download from.
This adds the new commands:
yt pasteboard --desc="Something" some_file.py
yt pastegrab PASTE_ID USERNAME
This automatically tosses it up. You get embed codes and some
highlights, but it's just easier to keep these things around than the
pastebin.
* The idea of enabling hgbb, cedit and ensuring a bitbucket user is
because I am of the opinion we should make it easier to fork the
repository to make changes. If those three are enabled, I believe a
command-line forking, editing of sources and so on, are all within our
reach.
* This bootstrap script requires that the yt-supplemental repo be
checked out in ${YT_DEST}/src/ . This repo is actually kind of cool,
in that it is a subrepo setup, and it pulls in a couple external
libraries that we can maintain. Right now it grabs the docs, the
cookbook, and the extensions mentioned above. This repo is now pulled
in the current install_script.sh.
Anyway, I am submitting this to the list to get some review. There
may be errors, but I have tested it quite a bit. It also informs the
user of what it's about to do and requires the user hit enter. At one
point it even asks for a yes or no.
The reason I am interested in this is that I think the idea of
bootstrapping people into a development environment is, generally, a
good idea. Particularly because some things -- like the pasteboard,
like forking, like contributing changes -- should be made really easy
and have the potential for a very high payoff. I hope I've motivated
things a bit better.
I was hoping that before I merged it I could get someone else to read
it over, maybe a couple people even to test it, and to get a good feel
for whether this is worthwhile or whether I should pull these changes
and just ignore the idea. What do people think?
Thanks,
Matt
