Kepler

Need a test case here.
Also, try selecting "Allow disconnected graphs" in the SDF director.

Ah, nevermind, I see the test cases.

I tried disconnected graphs, but it still throws the error.

I realize it's a slightly complicated case, as the scheduler would need to check up the chain of ports to see whether it's actually connected. Of course, that code might be useful in general. There's a problem with report design and ports from composite actors, and it might be at least partially related to identifying the actual source port.

This Ptolemy model has a top level with a const connected to one port of a two port composite. Inside the composite, the two ports are connected to the plus and minus ports of an AddSubtract and the output is connected to a Display.
When the model is run, the error message is:

ptolemy.actor.sched.NotSchedulableException: Actors remain that cannot be scheduled!

• SDF Graphs with feedback loops should have an actor with a delay in the loop, such as a SampleDelay.* The SDF director has an "allowDisconnectedGraphs"parameter, which, when true, permits disconnected SDF graphs.
• The token consumption rate and production rates might be mismatched. Usually, actors produce one token or consume one token on a port. To produce or consume multiple tokens per firing, add a "tokenConsumptionRate" or "tokenConsumptionRate" parameter to the appropriate port.
  For details, see the SDF chapter in Volume Three of the Ptolemy II design doc at http://ptolemy.eecs.berkeley.edu/ptolemyII/designdoc.htm
  Unscheduled actors:
  .sdfCompositeNoR.CompositeActor.Add or Subtract .sdfCompositeNoR.CompositeActor.Display
  Scheduled actors:
  .sdfCompositeNoR.Constant

The workaround is to not connect the inner connection that goes no where.
I'm not sure if this is a bug or an RFE. It is bug in that the model does
not behave as expected, even if the "Allow disconnected ports" is set.
It is an RFE in that the model has a disconnected port.

Original Bugzilla ID was 4519