[kepler-dev] Help with Pop Up Box in Kepler
subhav mital
mital.subhav at gmail.com
Fri Sep 4 14:08:31 PDT 2009
Hi Derik,
Thank for helping out. The only difference I can notice is regarding the
ptolemy folder.
I used the one which I checked out previously using the Kepler 1.0 dev
build.
I just copied pasted 'ptolemy' and not 'ptolemy-lib' from that folder to the
new folder. (The prev build still works fine, when I execute: ant run)
I wonder what is wrong, but definitely something is different/wrong here.
I'll use another OS/machine and try the same.
Thanks!
On Fri, Sep 4, 2009 at 4:08 PM, Derik Barseghian
<barseghian at nceas.ucsb.edu>wrote:
> Hi Subhav,
>
> I was able to get this to work on Windows Vista with the same procedure.
> I'm not sure what to recommend at this point beyond retrying from scratch.
> Maybe someone else could try a fresh checkout using the 'sanparks branch
> instructions' on a mac or linux and let us know what happens?
>
> Also, David or Chad, do you know what the problem is with the ptolemy
> checkout not working in this procedure?
>
> Derik
>
>
>
> On Sep 3, 2009, at 6:28 PM, Derik Barseghian wrote:
>
> Hi Subhav,
>>
>> I tried again and it still works for me, except for the part I mentioned
>> where I have to copy a ptolemy directory from another checkout. This is what
>> I did:
>>
>> mkdir Kepler
>> cd Kepler
>> svn co
>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
>> build-area
>> cd build-area
>> ant clean-cache
>> ant change-to -Dsuite=wrp -Dbranch=
>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
>> cp -r $KEPLER/ptolemy ../
>> ant update-ptolemy -Drev=54826
>> ant run
>>
>> I believe the versions of software you're using are fine.
>>
>> By the way, I'm still setting up Vista, I'll hopefully be able to test it
>> there tomorrow.
>>
>> Derik
>>
>>
>> On Sep 3, 2009, at 2:05 PM, subhav mital wrote:
>>
>> Hi Derik,
>>>
>>> I tried this on Ubuntu (Hardy Heron) and got the same error as on
>>> Windows. Guess I am doing something incorrect. Or maybe the build changed?
>>>
>>> Could you please retry again with the same build?
>>>
>>> I followed this procedure.
>>>
>>> mkdir Kepler
>>> svn co
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
>>> build-area
>>> cd build-area
>>> ant clean-cache
>>> ant change-to -Dsuite=wrp -Dbranch=
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
>>> ant update-ptolemy -Drev=54826
>>> ant run
>>>
>>> ( i used Java 1.5.0.16 for this, ant 1.7.1 and svn)
>>>
>>> Thank you.
>>>
>>>
>>> On Tue, Sep 1, 2009 at 1:27 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> The procedure is the same on linux. As I said, it worked for me on linux
>>> (ubuntu).
>>>
>>> Derik
>>>
>>>
>>>
>>> On Aug 31, 2009, at 7:26 PM, subhav mital wrote:
>>>
>>> Hi,
>>>
>>> Appreciate your help.
>>>
>>> Yes, it seems ok. (Below are the contents of the configuration file.)
>>> I've tried a clean multiple times but in vain.
>>>
>>> Could you please suggest steps to get this running on Linux?
>>>
>>> Thanks!!
>>>
>>>
>>> <?xml version="1.0" standalone="no"?>
>>> <!DOCTYPE entity PUBLIC "-//UC Berkeley//DTD MoML 1//EN"
>>> "http://ptolemy.eecs.berkeley.edu/xml/dtd/MoML_1.dtd">
>>> <entity name="configuration" class="ptolemy.actor.gui.Configuration">
>>> <doc>Configuration for Kepler</doc>
>>>
>>> <!--
>>> Help - About brings up the file specified by _about. The
>>> value of the
>>> _about attribute should be the same as the url property in
>>> welcomeWindow.xml FIXME: Unfortunately, the size of the
>>> about window
>>> is set in ptolemy/actor/gui/TableauFrame.java and not read
>>> from
>>> welcomeWindow.xml
>>> -->
>>> <property name="_about"
>>> class="ptolemy.kernel.attributes.FileAttribute"
>>> value="$CLASSPATH/ptolemy/configs/kepler/intro.htm" />
>>>
>>> <property name="_classesToRemove"
>>> class="ptolemy.data.expr.Parameter"
>>>
>>> value="{"ptolemy.codegen.kernel.StaticSchedulingCodeGenerator","ptolemy.codegen.c.kernel.CCodeGenerator"}">
>>> <doc>An array of Strings, where each element names a class
>>> to be
>>> removed by the MoMLFilter.</doc>
>>> </property>
>>>
>>> <!-- Specify copyright, used by actor/gui/GenerateCopyrights.java
>>> -->
>>> <property name="_applicationCopyright"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="ptolemy/configs/kepler/copyright.htm" />
>>>
>>> <!--
>>> Specify copyrights for actors, used by
>>> actor/gui/GenerateCopyrights.java
>>> -->
>>> <property name="_applicationCopyrights"
>>> class="ptolemy.data.expr.Parameter"
>>> value="{{actor="util.ImageJActor",
>>> copyright="imagej-copyright.htm"}}" />
>>>
>>> <!-- Specify file to be expanded, used by actor/gui/HTMLAbout.java
>>> -->
>>> <property name="_applicationDemos"
>>> class="ptolemy.data.expr.Parameter"
>>> value="{"ptolemy/configs/kepler/intro.htm"}" />
>>>
>>>
>>> <!--
>>> Specify icon, used by actor/gui/TableauFrame.java If you
>>> change the
>>> icon, update SplashScreen as well.
>>> -->
>>> <property name="_applicationIcon"
>>> class="ptolemy.kernel.attributes.FileAttribute"
>>>
>>> value="$CLASSPATH/ptolemy/configs/kepler/KeplerSmallIcon.gif" />
>>>
>>> <!--
>>> Specify an alternative action for the Drop action; class
>>> specified in
>>> 'value' should have a 'getMoml' method; called in the
>>> ptolemy/vergil/basic/EditorDropTarget class
>>> -->
>>> <property name="_alternateGetMomlAction"
>>> value="org.kepler.moml.GetMomlFromLSID"
>>> class="ptolemy.kernel.util.StringAttribute" />
>>>
>>>
>>>
>>> <!--
>>> Specify an alternative default directory to open when
>>> File|Open is
>>> first called; It is assumed that this directory is inside
>>> the $KEPLER
>>> directory called in the ptolemy/gui/Top class
>>> -->
>>> <property name="_alternateDefaultOpenDirectory"
>>> value="outreach/resources/demos/"
>>> class="ptolemy.kernel.util.StringAttribute" />
>>>
>>> <!-- Custom menu bar for Kepler -->
>>> <property name="_alternateTopPackClass"
>>> value="org.kepler.gui.KeplerMenuHandler"
>>> class="ptolemy.kernel.util.StringAttribute" />
>>>
>>> <!-- Custom actor menu items for kepler -->
>>> <!--
>>> <property name="_alternateActorInstanceController"
>>> value="org.kepler.gui.KeplerActorInstanceController"
>>> class="ptolemy.kernel.util.StringAttribute"/>
>>> -->
>>>
>>> <!-- Custom icon handler for kepler -->
>>> <property name="_alternateXMLIcon"
>>> value="org.kepler.gui.KeplerXMLIcon"
>>> class="ptolemy.kernel.util.StringAttribute" />
>>>
>>> <!--
>>> Specify name of this application, used by
>>> actor/gui/HTMLAbout.java
>>> -->
>>> <property name="_applicationName"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="Kepler" />
>>>
>>> <!-- Create a blank Graph Editor at start time. -->
>>> <!-- Used in VergilApplication.java-->
>>> <property name="_applicationBlankPtolemyEffigyAtStartup"
>>> class="ptolemy.data.expr.Parameter" value="true" />
>>>
>>> <!--
>>> Specify the help file to open. This file is at
>>> kepler/configs/ptolemy/configs/kepler/doc-index.htm
>>> -->
>>> <property name="_help"
>>> class="ptolemy.kernel.attributes.FileAttribute"
>>> value="$CLASSPATH/ptolemy/configs/kepler/doc-index.htm" />
>>>
>>> <!-- The directory of open models, each represented by an effigy.
>>> -->
>>> <!-- Note that this begins empty. -->
>>> <entity name="directory" class="ptolemy.actor.gui.ModelDirectory">
>>> </entity>
>>>
>>> <!-- Specify the name of the class that initializes the application.
>>> -->
>>> <property name="_applicationInitializer"
>>> class="ptolemy.data.expr.StringParameter"
>>> value="org.kepler.gui.KeplerInitializer" />
>>>
>>>
>>> <!-- Specify the name of the class that specializes the doc system.
>>> -->
>>> <property name="_docApplicationSpecializer"
>>> class="ptolemy.data.expr.Parameter"
>>> value="org.kepler.gui.KeplerDocApplicationSpecializer" />
>>>
>>> <!-- Specify the value of the docPreference for
>>> GetDocumentationAction.
>>> Used in ptolemy.vergil.basic.BasicGraphFrame. -->
>>> <property name="_getDocumentationActionDocPreference"
>>> class="ptolemy.data.expr.Parameter"
>>> value="1" />
>>>
>>> <!--
>>> Specify the remote location of the documentation. Used in
>>> ptolemy/vergil/actor/DocManager.java
>>> -->
>>> <property name="_remoteDocumentationURLBase"
>>> class="ptolemy.data.expr.Parameter"
>>> value="
>>> http://kepler-project.org/nightly/docResults/generatedJavadocs/" />
>>>
>>> <!--
>>> Specify weather multiple documentation windows are allowed
>>> at one time
>>> Used in the ptolemy/vergil/basic/GetDocumentationAction
>>> class
>>> -->
>>> <property name="_multipleDocumentationAllowed" value="true"
>>> class="ptolemy.kernel.util.StringAttribute" />
>>>
>>> <property name="karEntryHandlerFactory"
>>> class="org.kepler.kar.KAREntryHandlerFactory">
>>> <property name="amkeh"
>>> class="org.kepler.kar.handlers.ActorMetadataKAREntryHandler$Factory"/>
>>> <property name="layoutkeh"
>>> class="org.kepler.kar.handlers.ReportLayoutKAREntryHandler$Factory"/>
>>> <property name="rikeh"
>>> class="org.kepler.kar.handlers.ReportInstanceKAREntryHandler$Factory"/>
>>> <property name="wfrun"
>>> class="org.kepler.util.WorkflowRun$Factory"/>
>>> </property>
>>>
>>> <!-- The list of effigy factories, which defines what goes in -->
>>> <!-- the New menu, and also what sorts of files can be opened. -->
>>> <!-- These are searched in the order listed here, until one of -->
>>> <!-- the effigies agrees to open the file. -->
>>> <!-- Any of these effigies that return true to canCreateBlankEffigy
>>> -->
>>> <!-- will appear in the New menu. If there is a contained entity
>>> -->
>>> <!-- named "blank", then the effigy will initially refer to a clone
>>> -->
>>> <!-- of that blank entity. -->
>>> <entity name="effigyFactory"
>>> class="ptolemy.actor.gui.EffigyFactory">
>>> <!--
>>> MB changed this to point to our own version of
>>> graphEffigyFactory.xml, as a fix for Bug #2150 -
>>> see:
>>>
>>> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=2150
>>> -->
>>> <input source="ptolemy/graphEffigyFactory.xml" />
>>> <input source="ptolemy/configs/modalEffigyFactories.xml"/>
>>> <input source="ptolemy/configs/fsmEffigyFactories.xml" />
>>> <input source="ptolemy/configs/pteraEffigyFactory.xml"/>
>>> <input source="ptolemy/configs/gtEffigyFactory.xml"/>
>>> <input source="ptolemy/configs/iaEffigyFactory.xml" />
>>> <input source="ptolemy/configs/extendedEffigyFactories.xml"
>>> />
>>> </entity>
>>>
>>> <!-- The list of tableau factories, which defines the visual -->
>>> <!-- editors that are available. After an effigy is created -->
>>> <!-- for a model, these factories are tried in order until one -->
>>> <!-- is willing to open the model. Each editor contains a list -->
>>> <!-- of other editors that appear in the View menu. -->
>>> <property name="tableauFactory"
>>> class="ptolemy.actor.gui.TableauFactory">
>>> <input source="ptolemy/configs/gtTableauFactory.xml"/>
>>> <input source="ptolemy/configs/pteraTableauFactory.xml"/>
>>> <input source="ptolemy/configs/iaTableauFactory.xml" />
>>> <input source="ptolemy/configs/modalTableauFactory.xml"/>
>>> <input source="ptolemy/configs/fsmTableauFactory.xml" />
>>> <!--***controls the graph window***-->
>>> <input
>>> source="ptolemy/configs/kepler/graphTableauFactory.xml" />
>>> <!-- Add the code generator to the full configuration. -->
>>> <!--
>>> <property name="factory2"
>>> class="ptolemy.actor.gui.PtolemyTableauFactory">
>>> <property name="Code
>>> Generator"
>>> class="ptolemy.copernicus.gui.GeneratorTableau$Factory"/>
>>> </property>
>>> -->
>>> <input source="ptolemy/configs/extendedTableauFactories.xml"
>>> />
>>> </property>
>>>
>>> <!--
>>> The TabPane Extension Point allows Kepler to be configured
>>> with a certain
>>> set of graphical components that can be added to the
>>> interface through the
>>> ViewPane Kepler Extension Point. The classes
>>> specified must define their own internal Factory class that
>>> extends
>>> org.kepler.gui.TabPaneFactory. Specified classes must be a
>>> subclass of
>>> java.awt.Component and implement the org.kepler.gui.TabPane
>>> interface.
>>> -->
>>> <property name="tabPaneFactory"
>>> class="org.kepler.gui.TabPaneFactory">
>>> <!-- <property name="basicLibrary"
>>> class="org.kepler.gui.BasicLibraryPane$Factory" /> -->
>>> <property name="Components"
>>> class="org.kepler.gui.ComponentLibraryTab$Factory" />
>>> <property name="Components1"
>>> class="org.kepler.gui.ComponentLibraryTab$Factory" />
>>> <property name="Data"
>>> class="org.ecoinformatics.seek.ecogrid.quicksearch.DatasetPanel$Factory" />
>>> <property name="Items Of Interest"
>>> class="org.kepler.reporting.gui.ItemsOfInterestPanel$Factory" />
>>> <property name="Report Designer"
>>> class="org.kepler.reporting.gui.ReportDesignerPanel$Factory" />
>>> <property name="Report Viewer"
>>> class="org.kepler.reporting.gui.ReportViewerPanel$Factory" >
>>> <property
>>> name="_xslt"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="/xslt/rio2fo.xsl"/>
>>> </property>
>>> <property name="Report Contents"
>>> class="org.kepler.reporting.gui.ReportViewerTOC$Factory" />
>>> <property name="Properties"
>>> class="org.kepler.reporting.gui.PropertiesPanel$Factory" />
>>> <property name="Workflow Run Manager"
>>> class="org.kepler.workflowrunmanager.gui.WorkflowRunManagerPanel$Factory" />
>>> <property name="Outline"
>>>
>>> class="org.kepler.gui.WorkflowOutlineTabPane$Factory" />
>>> </property>
>>>
>>> <!--
>>> The ViewPane Extension Point allows developers to add their
>>> own layout
>>> of TabPanes to Kepler. Including more than one ViewPane
>>> here in the configuration
>>> will present the user with a selection box so they can
>>> switch between the views.
>>> Classes extending this extension point must specify their
>>> own
>>> internal Factory class that extends
>>> org.kepler.gui.ViewPaneFactory.
>>> Classes extending this extension point must be a subclass of
>>> java.awt.Container and implement the org.kepler.gui.ViewPane
>>> interface.
>>> TabPanes are added to views using the config.xml file, see
>>> the viewPaneTabPanes element there.
>>> -->
>>> <property name="viewPaneFactory"
>>> class="org.kepler.gui.ViewPaneFactory">
>>> <property name="Workflow Editor"
>>> class="org.kepler.gui.DefaultViewPane$Factory"/>
>>> <property name="Report Designer"
>>> class="org.kepler.gui.DefaultViewPane$Factory"/>
>>> <property name="Report Viewer"
>>> class="org.kepler.gui.DefaultViewPane$Factory"/>
>>> </property>
>>>
>>> <!--
>>> The preferencesTabFactory property will generate tabs in the
>>> preferences frame accessible in Kepler from the menu
>>> Tools->Preferences. All classes specified as sub properties
>>> to the
>>> preferencesTabFactory property will be added as tabs in the
>>> PreferencesFrame. The sub property names can be whatever you
>>> want,
>>> they are never used. The classes specified must define their
>>> own
>>> internal Factory class that extends PreferencesTabFactory.
>>> Specified
>>> classes must be a subclass of java.awt.Component and
>>> implement the
>>> org.kepler.gui.PreferencesTab interface.
>>> -->
>>> <property name="preferencesTabFactory"
>>> class="org.kepler.gui.PreferencesTabFactory">
>>> <property name="Components"
>>>
>>> class="org.kepler.gui.ComponentLibraryPreferencesTab$Factory" />
>>> <property name="Data"
>>>
>>> class="org.ecoinformatics.seek.ecogrid.EcogridPreferencesTab$Factory" />
>>> <!--
>>> <property name="Workflows"
>>>
>>> class="org.kepler.gui.WorkflowLibraryPreferencesTab$Factory" /> -->
>>> </property>
>>>
>>> <!-- enables scrollbars on the vergil canvas -->
>>> <property name="canvasNavigationModifier"
>>> class="org.kepler.gui.CanvasNavigationModifierFactory">
>>> <property name="scrollbars"
>>> class="org.kepler.gui.ScrollBarModifier$Factory" />
>>> </property>
>>>
>>> <!--
>>> enables the Kepler-specific right-click context menus for
>>> actors,
>>> directors etc. (but not for the workflow canvas - see
>>> "canvasContextMenuFactory"). To use old-style ptii
>>> right-click menus,
>>> delete or comment-out this entry:
>>> -->
>>>
>>> <property name="contextMenuFactory"
>>> class="ptolemy.vergil.basic.ContextMenuFactoryCreator">
>>> <property name="contextMenus"
>>>
>>> class="org.kepler.gui.KeplerContextMenuFactory$Factory" />
>>> </property>
>>>
>>> <!--
>>> enables the Kepler-specific right-click context menus for
>>> the workflow
>>> canvas (but not for actors, directors etc. - see
>>> "contextMenuFactory"). To use old-style ptii right-click
>>> menus, delete
>>> or comment-out this entry:
>>> -->
>>> <property name="canvasContextMenuFactory"
>>> class="ptolemy.vergil.basic.ContextMenuFactoryCreator">
>>> <property name="canvasContextMenus"
>>>
>>> class="org.kepler.gui.KeplerSchematicContextMenuFactory$Factory" />
>>> </property>
>>>
>>> <!--
>>> set to true if you want a component search to also search
>>> the ecogrid
>>> repository setup in the repositoryBundle.properties file
>>> labeled
>>> 'keplerRepository'
>>> -->
>>> <property name="ecogridComponentSearch"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="keplerRepository" />
>>>
>>> <!-- Configure the Actor Library by setting a custom LibraryBuilder
>>> -->
>>> <entity name="actor library" class="ptolemy.kernel.CompositeEntity">
>>>
>>> <entity name="Utilities"
>>> class="ptolemy.kernel.CompositeEntity">
>>> <property name="LocalPreferences"
>>> class="ptolemy.actor.gui.PtolemyPreferences" />
>>> </entity>
>>>
>>> <!-- Marker so that tree view expands the library. -->
>>> <property name="_libraryMarker"
>>> class="ptolemy.kernel.util.SingletonAttribute" />
>>>
>>> <!--
>>> This tells the system to use the alternative library
>>> builder. The
>>> KARLibraryBuilder searches the classpath for kar
>>> files and pulls any
>>> it finds into the cache.
>>> -->
>>> <property name="_alternateLibraryBuilder"
>>> value="org.kepler.moml.KARLibraryBuilder"
>>> class="ptolemy.kernel.util.StringAttribute">
>>> </property>
>>> </entity>
>>>
>>> <!--
>>> this property excludes certain properties from the
>>> docviewer. the
>>> syntax for the value is [exact|contains]:<name>. If exact is
>>> chosen,
>>> only a param with the exact name will be excluded. if
>>> contains is
>>> chosen, any param whose name contains the name string will
>>> be excluded
>>> -->
>>> <property name="docViewerExclude0"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="contains:semanticType" />
>>>
>>> <property name="docViewerExclude1"
>>> class="ptolemy.kernel.util.StringAttribute"
>>> value="exact:class" />
>>> </entity>
>>>
>>>
>>> On Mon, Aug 31, 2009 at 9:56 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> Sorry, not yet. I'm going to install Vista and try to determine what the
>>> problem is, but this might take me a few days as I have other things
>>> pending.
>>> I don't think it will help, but try a clean-all in your branch checkout's
>>> build-area, and then an ant run, just to be sure everything is clean.
>>> Also, the error message below makes it look like there's a problem with
>>> C:/Users/Subhav/Desktop/KeplerNew/wrp/configs/ptolemy/configs/kepler/configuration.xml.
>>> Are you able to open that file in a text editor and see that it hasn't been
>>> damaged? It should end with: </entity>
>>>
>>> Derik
>>>
>>>
>>> On Aug 31, 2009, at 6:46 PM, subhav mital wrote:
>>>
>>> Hi Derik,
>>>
>>> Any updates/suggestions on this?
>>>
>>> Thanks.
>>>
>>> On Fri, Aug 28, 2009 at 9:59 PM, subhav mital <mital.subhav at gmail.com>
>>> wrote:
>>> Hello,
>>>
>>> I've tried this twice now by creating a new folder and running through
>>> all enlisted steps. The error persists on Windows Vista.
>>>
>>> Is there any work around besides trying to deploy this on Linux?
>>>
>>> Thanks.
>>>
>>>
>>> On Thu, Aug 27, 2009 at 7:47 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav and kepler-dev,
>>>
>>> I'm trying the procedure (it used to work!) I gave you:
>>>
>>> 1) svn co
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
>>> build-area
>>> 2) cd build-area
>>> 3) ant clean-cache
>>> 4) ant change-to -Dsuite=wrp -Dbranch=
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
>>> 5) ant update-ptolemy -Drev=54826
>>> 6) ant run
>>>
>>>
>>> Like you, I got an error on step 5:
>>> [update-ptolemy] Error: /home/barseghian/dev3/kepler_branch/ptolemy does
>>> not exist.
>>>
>>>
>>> I noticed this error during step 4:
>>>
>>> [change-to] Downloading ptolemy...
>>> [change-to] Using ptolemy branch: ${ptolemyBranch}
>>> [change-to] svn co ${ptolemyBranch}
>>> /home/barseghian/dev3/kepler_branch/ptolemy
>>> [change-to] svn: '${ptolemyBranch}' does not appear to be a URL
>>> [change-to]
>>> [change-to] WARNING: It appears that the command did not execute properly
>>> and exited with an exit code of: 1
>>> [change-to] ptolemy-lib:
>>>
>>>
>>> Like I recommended to you, at this point I manually copied my ptolemy
>>> directory from my other kepler checkout (head), and then tried steps 5 and 6
>>> again. This didn't work for you (windows), but it did for me (linux): Kepler
>>> launched fine. I'm not sure why you got the error you pasted below. Yes,
>>> please try ant-clean cache and then ant run again.
>>>
>>> Does anyone else have ideas on what's wrong here?
>>>
>>> Derik
>>>
>>>
>>>
>>> On Aug 26, 2009, at 8:04 AM, subhav mital wrote:
>>>
>>> Hi Derik,
>>>
>>> Thanks for that. I did what we had discussed earlier and executed 'ant
>>> run'. Following is the error message -- stack trace -- I get:
>>>
>>>
>>> java.lang.Exception: Failed to parse "-kepler"
>>> at
>>> ptolemy.actor.gui.ConfigurationApplication.throwArgsException(ConfigurationApplication.java:635)
>>> at
>>> ptolemy.actor.gui.ConfigurationApplication.<init>(ConfigurationApplication.java:292)
>>> at ptolemy.actor.gui.MoMLApplication.<init>(MoMLApplication.java:81)
>>> at ptolemy.vergil.VergilApplication.<init>(VergilApplication.java:104)
>>> at ptolemy.vergil.VergilApplication$1.run(VergilApplication.java:194)
>>> at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209)
>>> at java.awt.EventQueue.dispatchEvent(EventQueue.java:461)
>>> at
>>> java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:242)
>>> at
>>> java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163)
>>> at
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157)
>>> at
>>> java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149)
>>> at java.awt.EventDispatchThread.run(EventDispatchThread.java:110)
>>> Caused by: java.lang.Exception: Failed to read configuration
>>> 'file:/C:/Users/Subhav/Desktop/KeplerNew/wrp/configs/ptolemy/configs/kepler/configuration.xml'
>>> at
>>> ptolemy.vergil.VergilApplication._createDefaultConfiguration(VergilApplication.java:286)
>>> at
>>> ptolemy.vergil.VergilApplication._createEmptyConfiguration(VergilApplication.java:322)
>>> at
>>> ptolemy.actor.gui.ConfigurationApplication._parseArgs(ConfigurationApplication.java:1109)
>>> at
>>> ptolemy.vergil.VergilApplication._parseArgs(VergilApplication.java:452)
>>> at
>>> ptolemy.actor.gui.ConfigurationApplication.<init>(ConfigurationApplication.java:226)
>>> ... 10 more
>>> Caused by: com.microstar.xml.XmlException: XML element "property"
>>> triggers exception:
>>> ptolemy.kernel.util.NameDuplicationException: Attempt to insert object
>>> named "_tableauFactory" into a container that already contains an object
>>> with that name. in
>>> file:/C:/Users/Subhav/Desktop/KeplerNew/ptolemy/target/classes/ptolemy/configs/fsmEffigyFactories.xml
>>> at line 30 and column 76
>>> Caused by:
>>> ptolemy.kernel.util.NameDuplicationException: Attempt to insert object
>>> named "_tableauFactory" into a container that already contains an object
>>> with that name.
>>> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:3385)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:921)
>>> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
>>> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
>>> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
>>> at com.microstar.xml.XmlParser.parseDocument(XmlParser.java:481)
>>> at com.microstar.xml.XmlParser.doParse(XmlParser.java:159)
>>> at com.microstar.xml.XmlParser.parse(XmlParser.java:132)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1414)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1370)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1331)
>>> at ptolemy.moml.MoMLParser._parse(MoMLParser.java:5922)
>>> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:2681)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:931)
>>> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
>>> at com.microstar.xml.XmlParser.parseContent(XmlParser.java:1104)
>>> at com.microstar.xml.XmlParser.parseElement(XmlParser.java:924)
>>> at com.microstar.xml.XmlParser.parseDocument(XmlParser.java:481)
>>> at com.microstar.xml.XmlParser.doParse(XmlParser.java:159)
>>> at com.microstar.xml.XmlParser.parse(XmlParser.java:132)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1414)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1350)
>>> at ptolemy.moml.MoMLParser.parse(MoMLParser.java:1300)
>>> at
>>> ptolemy.actor.gui.ConfigurationApplication.readConfiguration(ConfigurationApplication.java:408)
>>> at
>>> ptolemy.vergil.VergilApplication._createDefaultConfiguration(VergilApplication.java:284)
>>> ... 14 more
>>> Caused by: ptolemy.kernel.util.NameDuplicationException: Attempt to
>>> insert object named "_tableauFactory" into a container that already contains
>>> an object with that name.
>>> at ptolemy.kernel.util.NamedList.append(NamedList.java:133)
>>> at ptolemy.kernel.util.NamedObj._addAttribute(NamedObj.java:2073)
>>> at ptolemy.kernel.util.Attribute.setContainer(Attribute.java:398)
>>> at ptolemy.kernel.util.Attribute.<init>(Attribute.java:109)
>>> at ptolemy.kernel.util.Attribute.<init>(Attribute.java:86)
>>> at ptolemy.actor.gui.TableauFactory.<init>(TableauFactory.java:94)
>>> at
>>> ptolemy.vergil.fsm.modal.ModalTableauFactory.<init>(ModalTableauFactory.java:65)
>>> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
>>> Method)
>>> at
>>> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
>>> at
>>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
>>> at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
>>> at ptolemy.moml.MoMLParser._createInstance(MoMLParser.java:4180)
>>> at
>>> ptolemy.moml.MoMLParser._handlePropertyElement(MoMLParser.java:5411)
>>> at ptolemy.moml.MoMLParser.startElement(MoMLParser.java:2894)
>>> ... 42 more
>>>
>>> Maybe I will clean cache and try this again? Do you have any other
>>> suggestions?
>>>
>>> Thanks,
>>> Subhav
>>>
>>>
>>> On Tue, Aug 25, 2009 at 1:41 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> Sorry for the delay. I'm not sure why that happened.
>>> Yes, copying your existing ptolemy folder, and then executing ant
>>> update-ptolemy -Drev=54826 to move it back to the version that works with
>>> the kepler release-2.0.0-pre-alpha1-branch should work.
>>>
>>> Derik
>>>
>>>
>>>
>>> On Aug 22, 2009, at 9:56 PM, subhav mital wrote:
>>>
>>> Hi Derik,
>>>
>>> This is just what I followed and created a new folder where I checked out
>>> the new build.
>>> However, from the attached error.jpg image, it appears that Ptolemy
>>> modules did not get checked out. (Or was there an error in checking out the
>>> modules? )
>>>
>>> So would copying the ptolemy folder form the prev build to this folder
>>> and then executing ant update-ptolemy -Drev=54826 work fine?
>>>
>>> Thanks,
>>> Subhav
>>>
>>>
>>> On Thu, Aug 20, 2009 at 7:36 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> What I would recommend is keeping them completely separate -- do a
>>> check-out into a different directory for release-2.0.0-pre-alpha1-branch,
>>> and then copy the files you created in 1.0 into the appropriate location in
>>> this checkout. That way if it gives you problems, your kepler 1.0 checkout
>>> is completely untouched. One thing to note is that when you do an ant
>>> clean-cache or ant clean-all in the build-area of the
>>> release-2.0.0-pre-alpha1-branch checkout, it will delete ~/.kepler, just
>>> like would happen if you did an ant clean-cache or ant clean all in the
>>> build-area of your 1.0 checkout would do. You definitely want to issue an
>>> ant clean-cache when switching between trying 1.0 and
>>> release-2.0.0-pre-alpha1-branch, as the contents of .kepler will be
>>> incompatible.
>>>
>>> Derik
>>>
>>>
>>>
>>> On Aug 19, 2009, at 5:34 PM, subhav mital wrote:
>>>
>>> Thanks for your help.
>>>
>>> So as I understand, I can check out the new build, without disturbing the
>>> old one and switch between builds by using the ant change-to command. Would
>>> this still be possible after I do ant-clean cache as mentioned in the steps
>>> specified here:
>>>
>>>
>>> https://kepler-project.org/developers/teams/build/documentation/build-system-instructions
>>> #downloading-the-build
>>>
>>> Thanks.
>>>
>>>
>>>
>>>
>>> On Wed, Aug 12, 2009 at 2:24 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> I think that they will probably work, but it's possible that they won't.
>>> A lot of code has changed and been moved -- my guess is that you may just
>>> have to fix some of your import statements. If you're specifically relying
>>> on something we've changed, you may have problems. But you'd likely be
>>> facing those problems in the future anyways after we release 2.0 and if you
>>> wanted to upgrade. If bandwidth and harddrive space aren't an issue for you,
>>> I'd give it a try. Just keep the pre-alpha1 build separate from your current
>>> build in case you run into problems.
>>>
>>> Derik
>>>
>>>
>>>
>>> On Aug 11, 2009, at 11:14 PM, subhav mital wrote:
>>>
>>> Hi Derik,
>>>
>>> One concern: Will my self-created actors using Kepler-1.0 work in this
>>> latest build? Or would I have to recreate these actors again using the
>>> latest build?
>>>
>>> Thanks
>>>
>>>
>>> On Wed, Aug 12, 2009 at 1:54 AM, subhav mital <mital.subhav at gmail.com>
>>> wrote:
>>> Thanks so much. Will try this.
>>>
>>>
>>> On Tue, Aug 11, 2009 at 6:23 PM, Derik Barseghian <
>>> barseghian at nceas.ucsb.edu> wrote:
>>> Hi Subhav,
>>>
>>> I just checked and see the two bugs related to our below discussion are
>>> still open.
>>> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3930
>>> http://bugzilla.ecoinformatics.org/show_bug.cgi?id=3943
>>>
>>> Before I look into these to see if the problems still occur, let me ask:
>>> Is your current desire the same, to create and use two actors with
>>> Kepler-1.0? Since we have made many bug fixes and improvements to the
>>> development version of Kepler since we last spoke, if you don't need to user
>>> kepler-1.0 it might make sense for you to instead try working with our
>>> pre-alpha1-branch of Kepler. Setting up this branch requires the same
>>> assumptions be fulfilled as listed on the website for building the latest
>>> development version (
>>> https://kepler-project.org/developers/teams/build/documentation/build-system-instructions#assumptions),
>>> but to build the branch you instead use these commands:
>>>
>>> svn co
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch/modules/build-area
>>> build-area
>>> cd build-area
>>> ant clean-cache
>>> ant change-to -Dsuite=wrp -Dbranch=
>>> https://code.kepler-project.org/code/kepler/branches/release-2.0.0-pre-alpha1-branch
>>> ant update-ptolemy -Drev=54826
>>> ant run
>>>
>>> Derik
>>>
>>>
>>> <Error.jpg>
>>>
>>>
>>>
>>>
>>>
>>> ----------
>>> Derik Barseghian
>>> http://nceas.ucsb.edu/ecoinfo | office: 805-893-5127
>>> Rm 3411, Marine Science Research Building, UCSB
>>> Santa Barbara, CA, 93106-6150
>>>
>>>
>>>
>>>
>>>
>>>
>> ----------
>> Derik Barseghian
>> http://nceas.ucsb.edu/ecoinfo | office: 805-893-5127
>> Rm 3411, Marine Science Research Building, UCSB
>> Santa Barbara, CA, 93106-6150
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mercury.nceas.ucsb.edu/kepler/pipermail/kepler-dev/attachments/20090904/1dd62ddf/attachment-0001.html>
More information about the Kepler-dev
mailing list