Also, does

(into-array Double/TYPE data)

work?

If it does, it's not the ideal solution, but at least we could rule
out some possible causes...

Cheers,
M.


On 16 May 2012 20:11, Michał Marczyk <michal.marc...@gmail.com> wrote:
> Also, is the output of normalize transformed in any way before being
> passed on to the method which blow up?
>
> M.
>
>
> On 16 May 2012 20:09, Michał Marczyk <michal.marc...@gmail.com> wrote:
>> Could you replace (doubles data) in that troublesome spot with
>>
>> (doto (doubles data) ((comp prn class)))
>>
>> and note what gets printed?
>>
>> M.
>>
>>
>> On 16 May 2012 19:59, Jim - FooBar(); <jimpil1...@gmail.com> wrote:
>>> Yes that gave me a stack trace but it does not give me more info than i
>>> already know...For examlple i know the exception occurs at the call to
>>> analyze...the question is why? 'analyze' and 'process' both expect a
>>> double-array and a double-array is what 'normalize' delivers...
>>>
>>>
>>> ClassCastException [D cannot be cast to java.lang.Number
>>>     clojure.lang.Numbers.double_array (Numbers.java:1068)
>>>     clojure-encog.training/make-data/fn--963 (training.clj:37)
>>>     clojure-encog.examples/eval1041 (NO_SOURCE_FILE:1)
>>>     clojure.lang.Compiler.eval (Compiler.java:6511)
>>>     clojure.lang.Compiler.eval (Compiler.java:6477)
>>>     clojure.core/eval (core.clj:2797)
>>>     clojure.main/repl/read-eval-print--6405 (main.clj:245)
>>>     clojure.main/repl/fn--6410 (main.clj:266)
>>>     clojure.main/repl (main.clj:266)
>>>     clojure.tools.nrepl.middleware.interruptible-eval/evaluate/fn--337
>>> (interruptible_eval.clj:51)
>>>     clojure.core/apply (core.clj:601)
>>>     clojure.core/with-bindings* (core.clj:1771)
>>>
>>>
>>> Jim
>>>
>>>
>>> On 16/05/12 18:15, Aaron Cohen wrote:
>>>
>>> On Wed, May 16, 2012 at 1:04 PM, Jim - FooBar(); <jimpil1...@gmail.com>
>>> wrote:
>>>>
>>>> This is the only error I'm getting - there is no stack trace or at least i
>>>> can not see it...I'm inside leiningen 2 preview 4... I can however provide 
>>>> 2
>>>> screenshots confirming what is happening.
>>>
>>>
>>> Your most recent exception should be stored in "*e".
>>>
>>> To hopefully print a nice stack trace:
>>>
>>> (use 'clojure.repl)
>>> (pst)
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clojure@googlegroups.com
>>> Note that posts from new members are moderated - please be patient with your
>>> first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Clojure" group.
>>> To post to this group, send email to clojure@googlegroups.com
>>> Note that posts from new members are moderated - please be patient with your
>>> first post.
>>> To unsubscribe from this group, send email to
>>> clojure+unsubscr...@googlegroups.com
>>> For more options, visit this group at
>>> http://groups.google.com/group/clojure?hl=en

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to