Personal tools
You are here: Home
Log in


Forgot your password?
New user?
 

Modified items

All recently modified items, latest first.
Re: JDK 1.5 for Users? by sm, last updated: Jan 10, 2009 12:00 PM
Thanks for your help!
Re: proposed additions to provenance framework stores by Shawn Bowers, last updated: Jan 09, 2009 11:53 AM
Hi Matt:  Thanks for the reply. There seems to be a lot of detail in the docs in that directory. But, looking this over, I think I'm missing the "big picture". In particular, maybe you or Derik could give a two sentence, high-level statement saying what a ROML report is, and what type of information a report would contain.  Thanks!   Previously Matthew Jones wrote: Hey Shawn, There isn't a page for the reporting part of the work, but there is a directory in SVN with all of the reporting design documents.  It's here: https://code.kepler-project.org/code/kepler-docs/trunk/teams-and-wg/4-interest-groups/provenance/reporting/ The architecture overview is in the file "kepler_reporting_diagram.graffle". For ROML in n particular, you might look at the files "roml_layout.graffle", "schema/roml.xml", and "schema/riml.xml". Matt  
Re: proposed additions to provenance framework stores by Matthew Jones, last updated: Jan 09, 2009 09:44 AM
Hey Shawn, There isn't a page for the reporting part of the work, but there is a directory in SVN with all of the reporting design documents.  It's here: https://code.kepler-project.org/code/kepler-docs/trunk/teams-and-wg/4-interest-groups/provenance/reporting/ The architecture overview is in the file "kepler_reporting_diagram.graffle". For ROML in n particular, you might look at the files "roml_layout.graffle", "schema/roml.xml", and "schema/riml.xml". Matt
Re: proposed additions to provenance framework stores by Shawn Bowers, last updated: Jan 08, 2009 11:29 AM
I was wondering if there is any documentation on what the Report Object Model Language (ROML) is.  I am also generally curious w.r.t. reports, what type of information is envisioned to be included in a report.  Is there a write up or page that describes this? Thanks!
build system usability issues by Shawn Bowers, last updated: Jan 07, 2009 05:43 PM
I was wondering how to update modules in the new build system. In particular, lets say that I am using "vanilla-trunk", and notice that a few of the modules used in vanilla-trunk have been updated. Is there a way using a single svn or ant command to easily update these modules? Or, does each module have to be updated manually (by cd'ing into the module dir and running 'svn update', e.g.)?  It might be nice to have an ant command for this that updates all the modules in the active module list/suite.
Re: JDK 1.5 for Users? by Christopher Brooks, last updated: Jan 06, 2009 05:00 PM
Compiling the svn devel tree works with Java 1.6 (6.0), but a file must be copied.  Details are at http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3128 I don't think that it would be possible to run the prebuilt Kepler1.0.0 installer under Java 1.6 because of the problem outlined in bug 3128.  To use Java 1.6 would require a recompile.
Re: JDK 1.5 for Users? by Aaron Schultz, last updated: Jan 05, 2009 02:49 PM
Hi Subhav,  Yes JDK1.5 is required for Kepler at this time.
JDK 1.5 for Users? by sm, last updated: Dec 20, 2008 10:55 AM
Hey, Is JDK 1.5 (5.0) required for using Kepler or can the latest 6.0 version also work?
proposed additions to provenance framework stores by Derik Barseghian, last updated: Dec 19, 2008 07:21 PM
In discussing Reporting, the Workflow Run Manager , Publication Ready Archives and other additions to Kepler we've identified some things we'd like space made for within provenance framework datastores. I thought it would be good to list all these proposed additions in one place, and at the same time solicit feedback for others. This seems useful to do now, before "version1" provenance stores begin proliferating. At the same time we should be wary of bandwidth and store-sizes, and not add anything extraneous. So far I have: * LSID - or similar universal id to unambiguously id a run * workflow author * workflow tags * workflow description * ROML (report object model language) * RIO (report instance object) * report (e.g. in pdf form) More specific to my Workflow Run Manager-development needs, if you think a column to be searched against is sorely lacking in this mockup , please let me know. The Workflow Run Manager mockup page also has at top a diagram of what I believe is a fairly modern version of the kepler provenance framework sql schema. You can get an idea of what is stored by looking at this diagram.  
WRM Tag3 Bottom Tag Menu by Derik Barseghian, last updated: Dec 19, 2008 12:07 PM
WRM Tag3 Bottom Tag Menu
MyExperiment integration and support plan by Timothy McPhillips, last updated: Dec 17, 2008 04:51 PM
A draft plan for employing MyExperiment as a Kepler workflow sharing environment. Proposed tasks include enhancements both to Kepler and to MyExperiment.
Workflow Sharing Interest Group by Timothy McPhillips, last updated: Dec 16, 2008 04:43 PM
Re: review and revise the new web content by Ilkay Altintas, last updated: Dec 09, 2008 01:34 PM
I'm at the escience conference and the provenance challenge meeting is during our conference call time. It will probably be hard for me to get out. How about discussing it next week? -ilkay
Re: review and revise the new web content by Matthew Jones, last updated: Dec 09, 2008 12:31 PM
Hi Ilkay, I've edited some of my pages, but not all of them.  So I still need some more time on it.  But maybe we can touch base on this later today at our conference call, at least to get a status update? Matt
Re: review and revise the new web content by Ilkay Altintas, last updated: Dec 05, 2008 04:41 PM
What is our next step with this? Maybe have a discussion soon? -ilkay   Previously Matthew Jones wrote: Hi, As we discussed yesterday, here are the web pages for editing on the website, divided among those who volunteered to help. It'll be great to get a clean version of the site released so that we can remove the JSPwiki site.  Let's discuss these edits and changes in the User Rep forum. Thanks, Matt Mark ------- https://dev.kepler-project.org/users/the-kepler-project https://dev.kepler-project.org/users/downloads https://dev.kepler-project.org/users/projects-using-kepler https://dev.kepler-project.org/developers/reference/using-commons-logging https://dev.kepler-project.org/developers/reference/making-changes-to-the-kepler-wiki-account-and-password-information (probably can be deleted) https://dev.kepler-project.org/developers/reference/what-happens-when-kepler-starts-up Matt ------ https://dev.kepler-project.org/users/about-us https://dev.kepler-project.org/users/contact-us https://dev.kepler-project.org/developers/get-involved https://dev.kepler-project.org/developers/get-kepler-code https://dev.kepler-project.org/developers/reference/downloading-and-building-the-kepler-source-code https://dev.kepler-project.org/developers/reference/software-development-guidelines Tim ------ https://dev.kepler-project.org/users/features https://dev.kepler-project.org/users/sample-workflows https://dev.kepler-project.org/users/faq https://dev.kepler-project.org/developers/faq https://dev.kepler-project.org/developers/reference/adding-a-new-java-actor-to-kepler-a-quick-tutorial https://dev.kepler-project.org/developers/reference/adding-new-classes-jars-to-kepler https://dev.kepler-project.org/developers/reference/ptolemy-package-dependencies Ilkay ------ https://dev.kepler-project.org/users/documentation https://dev.kepler-project.org/users/publications https://dev.kepler-project.org/users/support https://dev.kepler-project.org/developers/reference/kepler-and-eclipse https://dev.kepler-project.org/developers/reference/executing-kepler-from-the-command-line https://dev.kepler-project.org/developers/reference/accessing-hsql https://dev.kepler-project.org/developers/reference/kepler-installer-checklist  
Re: The Repository Structure by Timothy McPhillips, last updated: Nov 20, 2008 03:29 PM
David played around with the idea of using svn:externals described in the previous post.  He created an externals.test module (https://code.kepler-project.org/code/kepler/modules/externals.test/trunk) and applied the following svn:externals property to it:    loader             https://code.kepler-project.org/code/kepler/modules/loader/trunk/ comad            https://code.kepler-project.org/code/kepler/modules/comad/trunk/   If you check out this directory from the repository, the loader and comad modules are included within it.  If you do an svn status or svn update in the local copy of this directory (above the loader and comad sub-directories), these commands descend into the loader and comad directories automatically.
The Repository Structure by David Welker, last updated: Nov 20, 2008 03:29 PM
Re: The Repository Structure by Timothy McPhillips, last updated: Nov 19, 2008 04:58 PM
Here's another idea for organizing the repository that may meet all of our needs and desires, and that takes advantage of the svn:external feature that, some time ago, Matt suggested might help us integrate our repository with Ptolemy's.  Matt and I also chatted very briefly about the idea of exploiting svn:external within our own repository a couple days ago.  Here's the proposal: 1.  We place all the modules in their own directories as is currently done at https://code.kepler-project.org/code/kepler/modules/.  Each module has it's own trunk, tags, and branches subdirectories.  This allows each module to be branched and tagged independently as needed by experimental and non-standard extensions to Kepler.  The build system is it's own 'module' with tags and branches like the rest.  So is 'core', 'util', and other modules that comprise the Kepler base system.  2.  We create an additional directory in the repository that represents a module 'suite' comprising the modules of the 'Kepler base system.'  Within this directory we use svn:external properties to point to the other modules in the repository that make up the Kepler base system, including a version of the build system. Checking out this virtual module thus grabs a copy of all the modules needed to build and run the Kepler base system as well as the version of the build system that goes with it.  One svn checkout command, ant run, and Kepler is running for the first time on a developer's machine.  All source code directories are version-controlled and can be updated; changes can be committed without any fuss. 3. On the local machine, checking out the base system is analogous to checking out the build system module now.  You can check out additional modules (either via svn or the 'get' target in the build system) into the top-level directory created in that first step.  The build system is configured as now, and one can switch quickly between configurations to be built as can be done now.  The difference is that the Kepler base system modules are checked out from the get-go, along with the build system.   One can also switch the version of a particular base system module on the local machine if needed. 4.  Adding a module to the base system is easy.  Just add another svn:external property to the Kepler base system directory.  We can also create alternative configurations of the base system by creating different module suites defined using the same mechanism.  Thoughts?
Interfaces to Provenance for REAP by Derik Barseghian, last updated: Nov 17, 2008 06:25 PM
Re: Interfaces to Provenance for REAP by Derik Barseghian, last updated: Nov 17, 2008 06:25 PM
Sounds good to me. Maybe a link to an overview page above the Emerging Approaches section. Previously Shawn Bowers wrote: Does this sound useful? Should we create this page? --shawn    
 
« Previous 20 items Next 20 items » 1 … 27 28 29 30 31 32 33 … 46