Bug #3332
closedRExpression_Matrix_IO_Test workflow gives an error
0%
Description
RExpression_Matrix_IO_Test workflow gives this error. This bug slipped into Kepler release too.
java.lang.NumberFormatException: For input string: "4L"
Problem sending to output port! java.lang.NumberFormatException: For input string: "4L"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
at java.lang.Integer.parseInt(Integer.java:456)
at java.lang.Integer.parseInt(Integer.java:497)
at org.ecoinformatics.seek.R.RExpression.setOutputToken(RExpression.java:852)
at org.ecoinformatics.seek.R.RExpression.getOutput(RExpression.java:798)
at org.ecoinformatics.seek.R.RExpression.fire(RExpression.java:739)
at ptolemy.actor.AtomicActor.iterate(AtomicActor.java:398)
at ptolemy.actor.sched.StaticSchedulingDirector.fire(StaticSchedulingDirector.java:188)
at ptolemy.actor.CompositeActor.fire(CompositeActor.java:400)
at ptolemy.actor.Manager.iterate(Manager.java:688)
at ptolemy.actor.Manager.execute(Manager.java:332)
at ptolemy.actor.Manager.run(Manager.java:1071)
at ptolemy.actor.Manager$3.run(Manager.java:1112)
Warning: '.RExpression_Matrix_IO_Test.Nonstrict Test' The test produced only 0 tokens, yet the correctValues parameter was expecting 1 tokens.
Updated by ben leinfelder almost 16 years ago
what version of R are you running?
I've got:
R version 2.6.2 (2008-02-08)
Copyright (C) 2008 The R Foundation for Statistical Computing
ISBN 3-900051-07-0
and am not seeing the error.
Updated by Derik Barseghian almost 16 years ago
I should note I'm seeing that error on stdout, not in the gui.
I have the same version of R as you on both Ubuntu and mac, and I'm seeing the error on both, both with head and the 1.0 release.
Updated by ben leinfelder almost 15 years ago
Derik - are you still seeing this bug?
I do not encounter the parsing error ("4L" etc...)
I believe we changed some things with respect to how this actor was dealing with int vs double representation.
can we consider closing this?
Updated by Derik Barseghian almost 15 years ago
Yep, I no longer see this bug on either Mac or Linux, closing.