Opened 8 years ago

Closed 7 years ago

#4394 closed defect (fixed)

PNLib problems with when(initial) and counter function

Reported by: Lennart Ochel Owned by: Lennart Ochel
Priority: high Milestone: 1.12.0
Component: Backend Version:
Keywords: PNlib Cc: Patrick Täuber, timo.lask@…

Description

It seems that the latest changes to wrapFunctionCalls broke the event handling for some models, e.g. PNlib.Examples.DisTest.TFDoutputConflict and PNlib.Examples.ExtTest.TFDStest.

Change History (5)

comment:1 by Patrick Täuber, 8 years ago

@lochel I think PNlib.Examples.ExtTest.TFDStest already fails with the changes from 2017-04-10

comment:2 by Lennart Ochel, 8 years ago

@ptaeuber You are right:

  • PNlib.Examples.ExtTest.TFDStest fails since 639c7bd
  • PNlib.Examples.DisTest.TFDoutputConflict fails since 2cb1d8f
Last edited 8 years ago by Lennart Ochel (previous) (diff)

comment:3 by Patrick Täuber, 8 years ago

Keywords: wrapFunctionCalls removed
Summary: wrapFunctionCalls and event handlingPNLib problems with when(initial) and counter function

The issue in PNlib.Examples.DisTest.TFDoutputConflict is caused by a different order of the parameter equations. Parameters are initialized differently now due to the PNlib.Functions.Random.counter() function, which returns the number of calls to that function.

comment:4 by Francesco Casella, 7 years ago

Milestone: 1.12.01.13.0

Milestone moved to 1.13.0 due to 1.12.0 already being released.

comment:5 by Martin Sjölund, 7 years ago

Milestone: 1.13.01.12.0
Resolution: fixed
Status: newclosed

This was fixed in the 1.12.0 release it seems.

Note: See TracTickets for help on using tickets.