Re: [Pipeline130-developers] Some tasks

[Nils H. <nil...@uc...>]

1. The manager does parse command line options and there are stubs in place
already!

2. I have a test script that works on the cluster using DRMAA.  I wont be
near a computer from Friday until after the exam so I apologize in advance.

3. Example XML files can be found on the cluster in $HOME/examples

Nils



On 5/12/09 7:47 PM, "cs...@uc..." <cs...@uc...> wrote:

> Hey guys,
> 
> I got an email from someone asking to be pointed in the right
> direction. Like I said, I'm going to try to get some concrete tasks
> written up in the bug tracker -- mainly code stuff but possibly
> documentation tasks as well. However, we should all also be
> contributing to the planning aspect. If you happen to see something
> that needs to be done, try to take note of it.
> 
> FIRST: please let us know immediately if you don't have SVN working.
> You really need to be able to check out the code.
> 
> Once you have it working, here are some things that need to be done:
> 
> Document stuff:
> Update the Design document to describe how we handle our Workflows. We
> have Workflow objects which contain Jobs, Jobs keep track of their own
> status, etc... the WFManager parses the XML documents into this
> structure, and we also serialize and transmit this structure as the
> main form of communication between Manager and Engine. When we query
> for Workflow status, we get a different structure that contains
> information specifically pertaining to job statuses. Maybe draw a
> diagram of these structures? This mailing list and the code itself are
> good places to look for info on these things.
> 
> Testing stuff:
> Design test cases, and try implementing them if possible! A good place
> to start would be testing Mike's workflow status printing routines,
> since they are pretty self-contained. Make a test scaffolding that
> generates a Workflow, populate it with Jobs that have interesting
> states, and print out the status. Make sure everything comes out
> looking right.
> 
> Coding stuff:
> Just try to dive in somewhere. Make small changes at first, then try
> adding functionality. The Engine->Cluster interface definitely needs
> work, but I think Nils is currently investigating -- that said, don't
> be shy to try getting it going yourself. As far as I know, the Manager
> currently parses command-line arguments but doesn't really examine
> them. If you could have it call different stub functions based on the
> command entered, that would be very helpful.
> 
> The Engine needs its entire "polling" loop done. You can just make an
> empty stub PollEngine() method and write the rest of the loop assuming
> that it updated the running workflows. Make sure you clearly mark
> which parts are unfinished!
> 
> -Chris
> 
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> Pipeline130-developers mailing list
> Pip...@li...
> https://lists.sourceforge.net/lists/listinfo/pipeline130-developers