[kepler-dev] ptexecute problems?

[Christopher Brooks]

Hi Dan,
It looks like a bug with ptolemy.actor.gui.PtExecuteApplication.

I usually use ptolemy.actor.gui.MoMLSimpleApplication instead of
PtExecuteApplication because MoMLSimpleApplication does not
extend MoMLApplication.

MoMLApplication unfortunately sets the UI look and feel, which forces
the process to try to connect to the X Server, which causes problems.

I'll look in to fixing PtExecuteApplication.  Sorry for the delay
on this, I did not realize that the ant ptexecute target used the
same class as the Ptolemy $PTII/bin/ptexecute script.

The problem can be replicated inside Ptolemy, without Kepler with:

bash-3.00$ cd $PTII/ptolemy/domains/sdf/kernel/test/auto/knownFailedTests
bash-3.00$ $PTII/bin/ptinvoke ptolemy.actor.gui.MoMLApplication tunneling2.xml 
Loaded file:/C:/cxh/ptII/lib/ptII.properties
bash-3.00$ $PTII/bin/ptinvoke ptolemy.actor.gui.MoMLSimpleApplication tunneling2.xml 
Command failed: ptolemy.kernel.util.IllegalActionException: Failed to compute schedule:
  in .tunneling2.SDF6
Because: No solution exists for the balance equations.
Graph is not consistent under the SDF domain detected on external port .tunneling2.typed composite actor0.port
ptolemy.kernel.util.IllegalActionException: Failed to compute schedule:
  in .tunneling2.SDF6
Because: No solution exists for the balance equations.
Graph is not consistent under the SDF domain detected on external port .tunneling2.typed composite actor0.port
      at ptolemy.domains.sdf.kernel.SDFDirector.preinitialize(SDFDirector.java:511)
      at ptolemy.actor.CompositeActor.preinitialize(CompositeActor.java:857)
      at ptolemy.actor.Manager.preinitializeAndResolveTypes(Manager.java:810)
      at ptolemy.actor.Manager.initialize(Manager.java:513)
      at ptolemy.actor.Manager.execute(Manager.java:311)

_Christopher
--------

    Hi All,
    
        I have been looking at the 'ptexecute' target in ant (more 
    accurately, I have been using 'ptexecute-dev' which, like 'run-dev' 
    avoids the long jar process in running the target.) I have been getting 
    some strange results.
    
        First of all, I created a test workflow called 'NonstrictTest.xml' 
    (in $KEPLER/workflows/test/). As configured, this trivial workflow has a 
    NonstrictTest actor that expects a result of '4'. It is connected to an 
    Expression actor that gives it a token equal to '5'. Thus, if you run 
    the workflow in Kepler, it throws an exception. However, if I execute
    
    ant ptexecute-dev -Dworkflow=C:/work/kepler/workflows/test/NonstrictTest.xm
   l
    
    this ant task runs and gives no indication of any problem!
    
    However, if I change the test workflow to execute OK (by changing the 
    input to the NonstrictTest actor), the ptexecute-dev task gives the result
    
         [java] 47 ms. Memory: 3136K Free: 491K (16%)
    
    (which is what one sees in the terminal window if the workflow executes 
    completely).
    
    So, my first problem is that ptexecute does not seem to generate any 
    error when the workflow fails!
    
        The next problem is with workflows that contain eml-datasources. All 
    of these immediately return with no indication of errors. However, there 
    are no messages from actors in the workflows subsequent to the 
    datasource. It looks like the datasource is just terminating the 
    execution of the workflow. I suspect that this is just due to ptexecute 
    not waiting for the initialization thread of the datasource to complete!
    
    So, it looks to me like we cannot use ptexecute to test workflow 
    operation (since there are not errors when there are exceptions), and 
    ptexecute cannot be used with datasources that use threads in 
    initialization!  (Of course, maybe I am missing something here; I 
    haven't really looked into the ptexecute code.)
    
    Dan
    
    -- 
    *******************************************************************
    Dan Higgins                                  higgins at nceas.ucsb.edu
    http://www.nceas.ucsb.edu/    Ph: 805-893-5127
    National Center for Ecological Analysis and Synthesis (NCEAS) Marine Scienc
   e Building - Room 3405
    Santa Barbara, CA 93195
    *******************************************************************
    
    
    _______________________________________________
    Kepler-dev mailing list
    Kepler-dev at ecoinformatics.org
    http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
--------