search

icyphy / ptII

Ptolemy II is an open-source software framework supporting experimentation with actor-oriented design.
https://ptolemy.eecs.berkeley.edu/ptolemyII
Other
99 stars 43 forks source link

expression 1E1 in DE director timeResolution property not interpreted correctly #170

Closed cxbrooks closed 15 years ago

cxbrooks commented 15 years ago

Note: the issue was created automatically with bugzilla2github tool

Original bug ID: BZ#240 From: Stavros Tripakis <stavros.tripakis@gmail.com> Reported version: 7.0 CC: bert.rodiers@gmail.com, pt-dev@chess.eecs.berkeley.edu

cxbrooks commented 15 years ago

Created attachment 28 the example showing the bug

The expression 1E1 in DE director timeResolution property not interpreted correctly: see attached model.

If the expression is replaced by 1.0 or 1E0 then it works correctly.

Sometimes it goes into an infinite loop (you need to add more components).

Attached file: DE-sum2-feedback.xml (text/xml, 4636 bytes) Description: the example showing the bug

cxbrooks commented 15 years ago

I'm not sure what the failure is here. I'm having a hard time explaining the outputs though.

timeResolution 10.0 10.0 20.0 30.0 40.0 ... 4.0 4.0 8.0 16.0 20.0 3.0 6.0 12.0 18.0 24.0 2.0 8.0 14.0 20.0 26.0 1.0 6.0 11.0 16.0 21.0

Maybe we can talk about this a group lunch, or pose it as an exam question in Edward's class.

BTW - run this model, start up Ptolemy and then do File->Open URL on https://chess.eecs.berkeley.edu/bugzilla/attachment.cgi?id=28 then save the model as DE-sum2-feedback.xml

cxbrooks commented 15 years ago

Hello Christopher,

The problem is the following. You can enter numbers with an negative exponent such as 1E-8, this works as you would expect, however if you start using a positive exponent, such as 1E1 the results are weird (sometimes the display wouldn't output any results). If you however don't use the scientific notation, it would work however.

cxbrooks commented 15 years ago

I believe this bug was not reproducible in the Ptolemy II devel tree. The 1E1 issue was likely a red herring. If this can be reproduced in the devel head, then please definitely reopen this bug.