[Yt-dev] Introducing the yt hub

Cameron Hummels chummels at astro.columbia.edu
Wed Aug 31 11:57:49 PDT 2011


Hey Matt,

I used this the other day to submit my "resubmit" script (for 
automatically resubmitting long enzo jobs to the kraken queue), and the 
yt hubsubmit script worked beautifully.  This will make it super easy 
for people to submit their own scripts and such to the hub for sharing 
with the community.  Great work!

Cameron

On 8/23/11 3:59 PM, Matthew Turk wrote:
> Hi all,
>
> To follow up on Britton's email, he and I have been working on
> automating and streamlining this process.  We have created a command,
> "hubsubmit", that will submit a mercurial repository to the Hub; it
> builds on the work of the "bootstrap_dev" command in getting users up
> and running on Bitbucket and with Mercurial.
>
> The idea is that if someone has created a set of scripts, or has an
> existing repository, it should be easy to submit that to the Hub.
>
> The command proceeds as follows:
>
>    * Check if a repository exists in the current working directory (or,
> optionally, the directory specified by --repo or -R)
>    * If not: prompt the user whether or not they would like to create
> one.  If so, create and import all current contents.  If not, quit.
>    * Check if a BitBucket URL is already in the set of paths in the
> repository; i.e., if it is a push alias.  If not, prompt the user for
> creating a repo on BitBucket and push to that location.
>    * Push to BitBucket URL.
>    * Prompt for Hub username/password
>    * Prompt for necessary hub submission stuff
>    * Submit!
>
> If you could test it out (and if you run into a low-hanging bug or
> ugliness, feel free to fix it!) that would be great.  Britton or I can
> remove any 'test' submissions you make along the way.
>
> The idea here is to make it ridiculously easy to submit to the Hub --
> just one step harder than the pastebin.  I think this is a good step
> in that direction, but I'd love some testing and suggestions!
>
> -Matt
>
>
> On Mon, Aug 22, 2011 at 10:37 AM, Britton Smith<brittonsmith at gmail.com>  wrote:
>> Good morning yt developers,
>>
>> I am very pleased to introduce to you all the yt hub:
>> http://hub.yt-project.org/.
>>
>> This was one of the main motivations for moving to yt-project.org.  Many
>> here might remember
>> the enzotools barn, which was a place for people to submit non-yt related
>> enzo scripts.  The
>> barn was very limited in scope and had somewhat poor usability since the
>> submission and
>> registration processes were not at all automated or simple.  Those days are
>> over.
>>
>> With the yt hub, users can create their own accounts and submissions
>> themselves.  We are
>> aiming for the yt hub to become the place to share all things related to
>> computational
>> astrophysics: yt scripts, simulation code specific scripts, relevant news
>> (like workshop
>> announcements), repositories of scripts for making figures from published
>> papers, etc.  Users
>> also have the option of subscribing to the hub, where they will receive
>> email alerts of new
>> submissions.
>>
>> Before we announce this to the full community, it would be great have the
>> site decently
>> populated with submissions.  If you have anything that you think other
>> people would be
>> interested in, please post it to the hub.  Currently, the recommended method
>> is to create
>> a repository somewhere like bitbucket and to submit the link to that.  If
>> you'd like to host
>> you submissions somewhere else, that's fine, too.
>>
>> All comments and feedback are welcome.  Hopefully, this can be something
>> really great.
>>
>> Britton
>> Matt
>>
>> _______________________________________________
>> Yt-dev mailing list
>> Yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
> _______________________________________________
> Yt-dev mailing list
> Yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>



More information about the yt-dev mailing list