Menu
▾
▴
pipeline130-developers — Developer Mailing List
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(37) |
May
(113) |
Jun
(62) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Chris S. <cs...@uc...> - 2009-05-10 03:02:14
|
Nils is working on getting the gnu.getopt package checked in to SVN. We're not totally sure how Java/Netbeans package management works so we're still figuring it out. In the meantime, you can just download the package locally. Better yet, check it in yourself so we all can benefit! -Chris -------------------------------------------------- From: "Mike Hess" <mh...@uc...> Sent: Saturday, May 09, 2009 6:12 PM To: "CS 130" <pip...@li...> Subject: [Pipeline130-developers] so i'm a netbeans noooob > How do I get the project to build? I think I'm missing the gnu.getopt > library. how do i get this? heres my error: > /Users/mhess/NetBeansProjects/trunk/wfmanager/src/wfmanager/ > MainSubmit.java:8: package gnu.getopt does not exist > import gnu.getopt.*; > > -Mike > > ------------------------------------------------------------------------------ > 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 > |
|
From: Nils H. <nil...@uc...> - 2009-05-10 02:23:14
|
In Java you cannot have nested block comments, in C/C++ you can. I have lived in the latter world for a while now... On 5/9/09 7:13 PM, "Mike Hess" <mh...@uc...> wrote: > I've seen both from professional programmers (much of apple's code for > instance.) Just a style difference. I personally don't like them but > I can live with them. What I'm used to is block comments for > documentation outside a function, then inside the functions, comments > using // so multiple segments of a function can be commented out, but > the code thats up has block comments for many of the lines inside a > function. > > > > -Mike > > > On May 9, 2009, at 6:53 PM, Nils Homer wrote: > >> Block comments are used for documentation: >> /** >> * @param ... >> */ >> >> Also, real programmers use block comments... >> >> On 5/9/09 6:26 PM, "Mike Hess" <mh...@uc...> wrote: >> >>> Haha sorry, just one of my pet-peeves. Rather then adding notes with >>> block comments I prefer just line comments (// rather than /* */) >>> Its just harder to comment out a section of code so I can get rid of >>> the stuff thats causing the compile errors ect, because the end of >>> the >>> block comments in the code stops my added ones. >>> >>> >>> -Mike >>> >>> ---------------------------------------------------------------------------- >>> -- >>> 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 >> >> >> >> ----------------------------------------------------------------------------->> - >> 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 > > > ------------------------------------------------------------------------------ > 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 |
|
From: Mike H. <mh...@uc...> - 2009-05-10 02:21:05
|
I've seen both from professional programmers (much of apple's code for instance.) Just a style difference. I personally don't like them but I can live with them. What I'm used to is block comments for documentation outside a function, then inside the functions, comments using // so multiple segments of a function can be commented out, but the code thats up has block comments for many of the lines inside a function. -Mike On May 9, 2009, at 6:53 PM, Nils Homer wrote: > Block comments are used for documentation: > /** > * @param ... > */ > > Also, real programmers use block comments... > > On 5/9/09 6:26 PM, "Mike Hess" <mh...@uc...> wrote: > >> Haha sorry, just one of my pet-peeves. Rather then adding notes with >> block comments I prefer just line comments (// rather than /* */) >> Its just harder to comment out a section of code so I can get rid of >> the stuff thats causing the compile errors ect, because the end of >> the >> block comments in the code stops my added ones. >> >> >> -Mike >> >> ------------------------------------------------------------------------------ >> 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 > > > > ------------------------------------------------------------------------------ > 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 |
|
From: Nils H. <nil...@uc...> - 2009-05-10 02:02:19
|
Block comments are used for documentation: /** * @param ... */ Also, real programmers use block comments... On 5/9/09 6:26 PM, "Mike Hess" <mh...@uc...> wrote: > Haha sorry, just one of my pet-peeves. Rather then adding notes with > block comments I prefer just line comments (// rather than /* */) > Its just harder to comment out a section of code so I can get rid of > the stuff thats causing the compile errors ect, because the end of the > block comments in the code stops my added ones. > > > -Mike > > ------------------------------------------------------------------------------ > 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 |
|
From: Mike H. <mh...@uc...> - 2009-05-10 01:26:41
|
Haha sorry, just one of my pet-peeves. Rather then adding notes with block comments I prefer just line comments (// rather than /* */) Its just harder to comment out a section of code so I can get rid of the stuff thats causing the compile errors ect, because the end of the block comments in the code stops my added ones. -Mike |
|
From: Mike H. <mh...@uc...> - 2009-05-10 01:13:15
|
How do I get the project to build? I think I'm missing the gnu.getopt library. how do i get this? heres my error: /Users/mhess/NetBeansProjects/trunk/wfmanager/src/wfmanager/ MainSubmit.java:8: package gnu.getopt does not exist import gnu.getopt.*; -Mike |
|
From: Nils H. <nil...@uc...> - 2009-05-09 22:25:44
|
I just installed the Java JDK so you can now compile java code on the cluster. Enjoy! Could everyone test out ssh'ing to the cluster and let me when you are successful? Nils |
|
From: Kenny W. <nak...@ho...> - 2009-05-09 06:32:41
|
Dear Group, Sorry I missed today's meeting. A family emergency happened and I had to drive back up to Norcal today. Can I get a rundown on what I missed? -Kenny _________________________________________________________________ Hotmail® has a new way to see what's up with your friends. http://windowslive.com/Tutorial/Hotmail/WhatsNew?ocid=TXT_TAGLM_WL_HM_Tutorial_WhatsNew1_052009 |
|
From: Nils H. <nil...@uc...> - 2009-05-09 05:47:10
|
I sent out an email to each of your sourceforge.net email addresses with the info to access the test cluster. Let me know if you did not receive the email. Also, here's a useful link giving examples of how to use DRMAA: http://gridengine.sunsource.net/howto/drmaa_java.html |
|
From: Nils H. <nil...@uc...> - 2009-05-08 16:59:57
|
I've noticed that some revisions (see revisions 24 and 25) do not include a description/log when committing code. This is a strict requirement in any development project. >From the command line you can include a log message: Svn commit -m "Message goes here" It is even easier with the netbeans IDE. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-04 17:47:43
|
The review document has been submitted. Also, the wiki now matches the review document. I have uploaded the Lyx source document to the the svn repository. If you have submitted any previous assignments could you please add them to the trunk/docs folder (source code, not the pdf)? For example, I added the Lyx document (latex editor) so that we can update it in the future. Adding the pdf would not be as helpful since we cannot easily edit the pdf. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-04 17:38:13
|
Also please do not use abbreviations like Don't You'll It's This is a formal document, and no employer would ever except this (at least our employer would not). Use instead: Do not You will It is Thanks, Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-04 17:29:15
|
Yes On 5/4/09 10:13 AM, "Chris Swan" <cs...@uc...> wrote: > I'm still editing the wiki -- should I stop now? > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Pipeline130-developers mailing list > Pip...@li... > https://lists.sourceforge.net/lists/listinfo/pipeline130-developers |
|
From: Chris S. <cs...@uc...> - 2009-05-04 17:13:59
|
I'm still editing the wiki -- should I stop now? |
|
From: Nils H. <nil...@uc...> - 2009-05-04 17:03:05
|
I will finish the review document now and upload it. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-03 06:41:33
|
I have the test cluster running. I will give you the user, password and hostname after class on Monday (since it isn't great to publicly advertise this). Also, I am using Netbeans as Chris recommended. Therefore the repository contains Netbeans project information, which will aid in our development. Please fix as necessary. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-02 21:48:38
|
Could you guys send me the docs (reqs and docs), or put them in the SVN docs directory with the project name, group member names, revision # (should be 0.1.1), page numbers, etc? I say we take a snapshot of these two documents every Monday and put them in the repository. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-02 21:40:56
|
I have update the design document on the wiki to include the templated XML schema as well as the Engine design. When you start coding, can you please keep updating the document. Also, considering the review, I removed the message with the other group's design/reqs documents, so lets still use the wiki to complete this review. If EVERYONE can add ONE criticism to the review document then we would be complete. Nils |
|
From: Nils H. <nil...@uc...> - 2009-05-02 20:18:01
|
This is rather annoying, but given the NDA for the review, we probably cannot use the wiki or this mailing list to send around their docs! Chris, can you remove the email from the archive if you can? Nils |
|
From: <cs...@uc...> - 2009-05-01 04:40:36
|
I posted an extension to your proposal at the bottom of that page. I think we should probably work it out some more tomorrow. I made a study room reservation for us in Powell Library tomorrow, 12:30-2:30. The room has a whiteboard and a computer with a giant TV. We don't have to use it, but I figured it'd be nice to have the option. I don't have any whiteboard markers though, so if anyone does, can you bring them? Also, a few days ago I sent out the design doc and requirements from group 8, but I think the listserv may have rejected it. Did anyone receive it? We are supposed to review it by Monday. Let me know if it didn't go through and I will host it somewhere and link to it. -Chris Quoting Nils Homer <nil...@uc...>: > I am starting to work on the XML schema (see link below) and the > WorkflowXMLReader Java class. Could you take a look at the incomplete > schema I came up with and lets finalize on Friday? > > XML schema: > https://apps.sourceforge.net/mediawiki/pipeline130/index.php?title=Workflow_ > XSD > > Also, lets figure out the internal design (interface and classes) for the > Engine and Manager on Friday (2hr power meeting). Does this sound > reasonable? > > Nils > > > > ------------------------------------------------------------------------------ > Register Now & Save for Velocity, the Web Performance & Operations > Conference from O'Reilly Media. Velocity features a full day of > expert-led, hands-on workshops and two days of sessions from industry > leaders in dedicated Performance & Operations tracks. Use code vel09scf > and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf > _______________________________________________ > Pipeline130-developers mailing list > Pip...@li... > https://lists.sourceforge.net/lists/listinfo/pipeline130-developers > |
|
From: Nils H. <nil...@uc...> - 2009-04-30 05:17:25
|
I am starting to work on the XML schema (see link below) and the WorkflowXMLReader Java class. Could you take a look at the incomplete schema I came up with and lets finalize on Friday? XML schema: https://apps.sourceforge.net/mediawiki/pipeline130/index.php?title=Workflow_ XSD Also, lets figure out the internal design (interface and classes) for the Engine and Manager on Friday (2hr power meeting). Does this sound reasonable? Nils |
|
From: Nils H. <nil...@uc...> - 2009-04-28 17:12:01
|
FYI, the test cluster should be up by tomorrow night at the latest, Nils |
|
From: Mike H. <mh...@uc...> - 2009-04-28 00:21:11
|
I added a Programming Style page to the wiki. Add your ideas/comments for the programming style page. Also if someone can clean it up to make it look neater that would be useful. Most of the ideas I put up there were from this website: http://www.student.cs.uwaterloo.ca/~cs132/Resources/StyleGuide.html . Here is the link to the wiki: https://apps.sourceforge.net/mediawiki/pipeline130/index.php?title=Programming_Style -Mike |
|
From: Nils H. <nil...@uc...> - 2009-04-27 20:24:04
|
I would be happy to work on the DRMAA interface into the cluster (the Workflow engine); let me know if this is a problem. I could use one or two more people to help programming our engine to interact with the DRMAA API. You should read the DRMAA manual: http://www.ogf.org/documents/GFD.130.pdf We need to start assigning programming tasks, so think of what you want to contribute. I would propose the following Object Orientated abstraction in the Engine. 1. The engine fundamentally forms a queue of Workflow objects (Workflow class). To check the status of a workflow, it only needs to iterate through this queue. 2. Each workflow class is composed of jobs (nodes). The workflow simply needs to store a list representing the canonical ordering of the jobs (nodes). 3. Each node stores the bulk of the necessary information. 3.a COMMAND: stores the "command", including I/O path, path to script, command line arguments, etc. 3.b NODE PROPERTIES: stores references to incoming nodes, outgoing nodes, and whether the have received confirmations (ok to run) from incoming nodes, whether it has sent confirmations to child nodes. 4. The engine maintains a list of jobs IDS that it has submitted (for tracking). Once a job completes (fails, succeeds, or aborted), the engine transfers this status to the workflow. The workflow class signals the correct node of the status. The node then acts accordingly (signals children, throws an exception, returns a status etc.). I think this message passing scheme: DRMAA <-> ENGINE ENGINE <-> WORKFLOW WORKFLOW <-> NODE Works well and should be easy to implement. What do you guys think? Nils |
|
From: Chris S. <cs...@uc...> - 2009-04-27 12:21:37
|
I just submitted copies of the presentation and design document due today. Hopefully I don't totally mess up the presentation! I need sleep! -Chris |
6 messages has been excluded from this view by a project administrator.
