jactr-users Mailing List for jACT-R
Status: Beta
Brought to you by:
amharrison
You can subscribe to this list here.
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
(3) |
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Anthony H. <amh...@gm...> - 2011-05-31 18:48:31
|
Christian, This is not a known issue. I'll create a bug report for it, but I am unable to reproduce using the latest builds. A common issue that window's users report is that spaces in their path names can cause problems. Some code (read as: not mine, as far as I know) doesn't encode URLs with spaces correctly. But that error has a different pattern. Let's take a look at some of the logs to see what's what. 1) enable logging for the model. Under the run configuration for the count model, select the Logging/Trace tab and check enable jACT-R logging. (this is the source code level logging). After the failed run, their should be a jactr-error.log file in the runs/${date}/${time} directory. 2) After a failed run check in ${userHome}/.jactr/configuration/org.jactr.tutorial.unit1/count-actual/. If there are any log files in the directory, send them my way. (the .jactr/ holds cached information that allows subsequent runs to execute faster). If something catastrophic happens before the jACT-R code is even reached (which this sounds like it could be), that log will contain the details. On Sun, May 29, 2011 at 10:06 AM, <dit...@st...> wrote: > Dear jACT-R Users, > > I'm currently evaluating some cognition frameworks with my fellow students > and came across jACT-R. With your installation guide I could set it up > successfully. After running the eclipse environment, I chose the Unit 1 > tutorial linked in the welcome screen, because we had executed it on the > original Lisp ACT-R before and wanted to see what jACT-R was doing with > it. Everything works fine until the run step for the count model. When > running the count model the eclipse environment just jumps to 100% CPU > utilization and hangs up. It seems that the simulation is doing some steps > before hanging up. > > Is this a known issue? And are there any solutions for that? > > I tried to go back to older jACT-R versions, but couldn't get a successful > run with the count model. I also tried the solution described here: > http://jactr.org/node/110 . It didn't work either. We tried different > eclipse versions (3.6, 3.6.2), java versions (1.6.21, 1.6.25; 32 and 64 > bit with Win 7 64-bit), OS versions (Win 7 64-bit, Win 7 32-bit, Win XP > Pro 32-bit). Nothing did work. > > I did use the following jACT-R plugins: > org.jactr.doc_1.0.1.201010131208 > org.jactr.eclipse.association.ui.source_1.0.0.201009141358.jar > org.jactr.eclipse.association.ui_1.0.0.201009141358.jar > org.jactr.eclipse.bundles.source_1.0.1.201009151423.jar > org.jactr.eclipse.bundles_1.0.1.201009151423.jar > org.jactr.eclipse.compilers.source_1.0.0.201009151423.jar > org.jactr.eclipse.compilers_1.0.0.201009151423.jar > org.jactr.eclipse.core.source_1.2.8.201009151423.jar > org.jactr.eclipse.core_1.2.8.201009151423.jar > org.jactr.eclipse.demo.source_0.1.0.201009151423.jar > org.jactr.eclipse.demo_0.1.0.201009151423.jar > org.jactr.eclipse.doc_1.0.8.201009151423 > org.jactr.eclipse.execution.source_1.0.0.201009151423.jar > org.jactr.eclipse.execution_1.0.0.201009151423.jar > org.jactr.eclipse.ortho.ui.source_1.0.0.201009151423.jar > org.jactr.eclipse.ortho.ui_1.0.0.201009151423.jar > org.jactr.eclipse.production.source_1.0.0.201009141358.jar > org.jactr.eclipse.production_1.0.0.201009141358.jar > org.jactr.eclipse.runtime.source_1.2.8.201009151423.jar > org.jactr.eclipse.runtime.ui.probe.source_1.0.1.201009151423.jar > org.jactr.eclipse.runtime.ui.probe_1.0.1.201009151423.jar > org.jactr.eclipse.runtime.ui.source_1.2.8.201009151423.jar > org.jactr.eclipse.runtime.ui_1.2.8.201009151423.jar > org.jactr.eclipse.runtime_1.2.8.201009151423.jar > org.jactr.eclipse.ui.source_1.2.8.201009151423.jar > org.jactr.eclipse.ui_1.2.8.201009151423.jar > org.jactr.io.source_1.0.9.201010071152.jar > org.jactr.io_1.0.9.201010071152 > org.jactr.launching.source_1.0.1.201009171107.jar > org.jactr.launching_1.0.1.201009171107.jar > org.jactr.modules.temporal.source_1.0.0.201009171107.jar > org.jactr.modules.temporal_1.0.0.201009171107.jar > org.jactr.modules.threaded.source_1.0.0.201009171107.jar > org.jactr.modules.threaded_1.0.0.201009171107.jar > org.jactr.source_1.2.15.201010131208.jar > org.jactr.support_1.2.2.201009171107 > org.jactr.tools.masterslave.source_1.0.1.201009171107.jar > org.jactr.tools.masterslave_1.0.1.201009171107.jar > org.jactr.tools.shell.source_1.0.1.201009171107.jar > org.jactr.tools.shell_1.0.1.201009171107 > org.jactr.tools.source_1.0.6.201009171107.jar > org.jactr.tools_1.0.6.201009171107 > org.commonreality.doc_1.0.0.201009071211.jar > org.commonreality.mina.source_1.1.0.201009071211.jar > org.commonreality.mina_1.1.0.201009071211.jar > org.commonreality.sensors.base.source_1.0.0.201009071211.jar > org.commonreality.sensors.base_1.0.0.201009071211.jar > org.commonreality.sensors.swing.source_1.0.0.201009071211.jar > org.commonreality.sensors.swing_1.0.0.201009071211.jar > org.commonreality.sensors.xml.source_1.0.0.201009071211.jar > org.commonreality.sensors.xml_1.0.0.201009071211.jar > org.commonreality.source_1.2.8.201009071211.jar > > If anyone could help us with this problem, any help would be appreciated. > > Best Regards > Christian Dittrich > > -- ----- Anthony M. Harrison, PhD http://anthonymharrison.com/ http://jactr.org |
From: <dit...@st...> - 2011-05-29 14:22:09
|
Dear jACT-R Users, I'm currently evaluating some cognition frameworks with my fellow students and came across jACT-R. With your installation guide I could set it up successfully. After running the eclipse environment, I chose the Unit 1 tutorial linked in the welcome screen, because we had executed it on the original Lisp ACT-R before and wanted to see what jACT-R was doing with it. Everything works fine until the run step for the count model. When running the count model the eclipse environment just jumps to 100% CPU utilization and hangs up. It seems that the simulation is doing some steps before hanging up. Is this a known issue? And are there any solutions for that? I tried to go back to older jACT-R versions, but couldn't get a successful run with the count model. I also tried the solution described here: http://jactr.org/node/110 . It didn't work either. We tried different eclipse versions (3.6, 3.6.2), java versions (1.6.21, 1.6.25; 32 and 64 bit with Win 7 64-bit), OS versions (Win 7 64-bit, Win 7 32-bit, Win XP Pro 32-bit). Nothing did work. I did use the following jACT-R plugins: org.jactr.doc_1.0.1.201010131208 org.jactr.eclipse.association.ui.source_1.0.0.201009141358.jar org.jactr.eclipse.association.ui_1.0.0.201009141358.jar org.jactr.eclipse.bundles.source_1.0.1.201009151423.jar org.jactr.eclipse.bundles_1.0.1.201009151423.jar org.jactr.eclipse.compilers.source_1.0.0.201009151423.jar org.jactr.eclipse.compilers_1.0.0.201009151423.jar org.jactr.eclipse.core.source_1.2.8.201009151423.jar org.jactr.eclipse.core_1.2.8.201009151423.jar org.jactr.eclipse.demo.source_0.1.0.201009151423.jar org.jactr.eclipse.demo_0.1.0.201009151423.jar org.jactr.eclipse.doc_1.0.8.201009151423 org.jactr.eclipse.execution.source_1.0.0.201009151423.jar org.jactr.eclipse.execution_1.0.0.201009151423.jar org.jactr.eclipse.ortho.ui.source_1.0.0.201009151423.jar org.jactr.eclipse.ortho.ui_1.0.0.201009151423.jar org.jactr.eclipse.production.source_1.0.0.201009141358.jar org.jactr.eclipse.production_1.0.0.201009141358.jar org.jactr.eclipse.runtime.source_1.2.8.201009151423.jar org.jactr.eclipse.runtime.ui.probe.source_1.0.1.201009151423.jar org.jactr.eclipse.runtime.ui.probe_1.0.1.201009151423.jar org.jactr.eclipse.runtime.ui.source_1.2.8.201009151423.jar org.jactr.eclipse.runtime.ui_1.2.8.201009151423.jar org.jactr.eclipse.runtime_1.2.8.201009151423.jar org.jactr.eclipse.ui.source_1.2.8.201009151423.jar org.jactr.eclipse.ui_1.2.8.201009151423.jar org.jactr.io.source_1.0.9.201010071152.jar org.jactr.io_1.0.9.201010071152 org.jactr.launching.source_1.0.1.201009171107.jar org.jactr.launching_1.0.1.201009171107.jar org.jactr.modules.temporal.source_1.0.0.201009171107.jar org.jactr.modules.temporal_1.0.0.201009171107.jar org.jactr.modules.threaded.source_1.0.0.201009171107.jar org.jactr.modules.threaded_1.0.0.201009171107.jar org.jactr.source_1.2.15.201010131208.jar org.jactr.support_1.2.2.201009171107 org.jactr.tools.masterslave.source_1.0.1.201009171107.jar org.jactr.tools.masterslave_1.0.1.201009171107.jar org.jactr.tools.shell.source_1.0.1.201009171107.jar org.jactr.tools.shell_1.0.1.201009171107 org.jactr.tools.source_1.0.6.201009171107.jar org.jactr.tools_1.0.6.201009171107 org.commonreality.doc_1.0.0.201009071211.jar org.commonreality.mina.source_1.1.0.201009071211.jar org.commonreality.mina_1.1.0.201009071211.jar org.commonreality.sensors.base.source_1.0.0.201009071211.jar org.commonreality.sensors.base_1.0.0.201009071211.jar org.commonreality.sensors.swing.source_1.0.0.201009071211.jar org.commonreality.sensors.swing_1.0.0.201009071211.jar org.commonreality.sensors.xml.source_1.0.0.201009071211.jar org.commonreality.sensors.xml_1.0.0.201009071211.jar org.commonreality.source_1.2.8.201009071211.jar If anyone could help us with this problem, any help would be appreciated. Best Regards Christian Dittrich |
From: <amh...@gm...> - 2010-11-17 15:52:10
|
Martijn, So, I was able to reproduce the error message. Looking closely at it, I've determined that it is that red-herring I'd mentioned. Because logging and IDE interfacing is done asynchronously (to limit the impact on the model's execution speed), messages may be logged after the IDE (or the runtime) determines that it should shutdown. The model itself, runs fine. I've updated the code to log this exception to debug so it won't be as in your face. I'll investigate adding an IDE synchronization point to the end of the model run. As for the remaining processes (Log Propogation) - that would have been from your prior run and would have timed-out in a minute or so. It looks like what was happening for you was that the model runs and exits so quickly, that the messages bound for the IDE are being lost (due to the rejected execution). Because the IDE never gets those initial messages, it sits there spinning waiting. It will timeout and report the that the model never started. A model that actually runs a bit longer should not exhibit any of this (knock on wood). If you continue to have a problem, there is code for synchronizing with the IDE that can be repurposed to address this, but it comes at the cost of increased processing time, so I'm reluctant to use it right now. -tony |
From: Martijn B. <mb8...@gm...> - 2010-11-15 22:52:17
|
Dear jACT-R users, I've encountered a peculiar phenomenon while using the new version of jACT-R in Helios. I was wondering if you could shed some light on it's origin. It first started happening in a project I was working on, so in order to confirm that it was caused by my code I set up: A fresh installation of Helios (incl. jACT-R) and a generated jACT-R project (in an empty workspace). However, even without any of my own code, I consistently get the following exception, before any other output is given: [ERROR] ACTREventDispatcher - Uncaught exception during event firing of org.jactr.core.module.procedural.event.ProceduralModuleEvent@b05acd to org.jactr.tools.tracer.listeners.LogTracer$1@1989b5<java.util.concurrent.RejectedExecutionException>java.util.concurrent.RejectedExecutionException at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(Unknown Source) at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Unknown Source) at org.jactr.tools.tracer.sinks.NetworkedSink.scheduleFlush(NetworkedSink.java:114) at org.jactr.tools.tracer.sinks.NetworkedSink.add(NetworkedSink.java:138) at org.jactr.tools.tracer.listeners.BaseTraceListener.sink(BaseTraceListener.java:90) at org.jactr.tools.tracer.listeners.LogTracer.flushToSink(LogTracer.java:112) at org.jactr.tools.tracer.listeners.LogTracer$1.conflictSetAssembled(LogTracer.java:54) at org.jactr.core.module.procedural.event.ProceduralModuleEvent.fire(ProceduralModuleEvent.java:120) at org.jactr.core.module.procedural.event.ProceduralModuleEvent.fire(ProceduralModuleEvent.java:1) at org.jactr.core.event.ACTREventDispatcher$Pair$1.run(ACTREventDispatcher.java:140) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at org.commonreality.executor.GeneralThreadFactory$1.run(GeneralThreadFactory.java:88) at java.lang.Thread.run(Unknown Source) I thought it might be caused by the lack of productions and chunks, so I added them. However, after that, the model always gets stuck at 57% of building the actual. A second process is also visible in the progress view called: Log propogation. The exception does not show up in the Error Log view. Is this something you have seen before? Could you point me in the direction of the answer? Kind Regards, Martijn |
From: Anthony M. H. <amh...@gm...> - 2010-11-14 16:16:40
|
I'm on the road right now. I'll be able to address this tomorrow. Two things: 1. let's move this to the mailing list (https://lists.sourceforge.net/lists/listinfo/jactr-users) for documentation purposes 2. This is reliably reproducible? The exception in the log is likely a red herring. I thought I was redirecting those exceptions to the debug log. Rejected executions occur when a log event propagation occurs after the runtime has scheduled a shutdown (possible since logging is asynchronous). Is there anything in the IDE's error log? (check the Error View) Sent from my iPad, please excuse my typos. On Nov 14, 2010, at 6:34 AM, Martijn Brakenhoff <mar...@gm...> wrote: > Dear Tony, > > I've encountered a peculiar phenomenon while using the new version > of jACT-R in Helios. I was wondering if you could shed some light on > it's origin. > > Using a fresh installation of Helios (incl. jACT-R) and a generated > jACT-R project (in an empty workspace) I get the following exception: > > [ERROR] ACTREventDispatcher - Uncaught exception during event firing of org.jactr.core.module.procedural.event.ProceduralModuleEvent@b05acd to org.jactr.tools.tracer.listeners.LogTracer$1@1989b5 <java.util.concurrent.RejectedExecutionException>java.util.concurrent.RejectedExecutionException > at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor.reject(Unknown Source) > at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(Unknown Source) > at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(Unknown Source) > at java.util.concurrent.Executors$DelegatedScheduledExecutorService.schedule(Unknown Source) > at org.jactr.tools.tracer.sinks.NetworkedSink.scheduleFlush(NetworkedSink.java:114) > at org.jactr.tools.tracer.sinks.NetworkedSink.add(NetworkedSink.java:138) > at org.jactr.tools.tracer.listeners.BaseTraceListener.sink(BaseTraceListener.java:90) > at org.jactr.tools.tracer.listeners.LogTracer.flushToSink(LogTracer.java:112) > at org.jactr.tools.tracer.listeners.LogTracer$1.conflictSetAssembled(LogTracer.java:54) > at org.jactr.core.module.procedural.event.ProceduralModuleEvent.fire(ProceduralModuleEvent.java:120) > at org.jactr.core.module.procedural.event.ProceduralModuleEvent.fire(ProceduralModuleEvent.java:1) > at org.jactr.core.event.ACTREventDispatcher$Pair$1.run(ACTREventDispatcher.java:140) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at org.commonreality.executor.GeneralThreadFactory$1.run(GeneralThreadFactory.java:88) > at java.lang.Thread.run(Unknown Source) > > I thought it might be caused by the lack of productions and chunks, > so I added them. However, after that, the model always gets stuck > at 57% of building the actual. A second process is also visible in > the progress view called: Log propogation. > > Is this something you have seen before? Could you point me in the > direction of the answer? > > Kind Regards, > > Martijn |
From: Roy W. <js...@gm...> - 2010-09-20 21:14:01
|
The good news is that I was able to install the unit1 tutorial project and run a model. The not as good news is that I was (using helios-rcp on Windoze XP) to import the *ZIP* archive without first creating a jACTR project. However, the zipped project was imported as a folder under X. After fiddling unsuccessfully for awhile to run the count model under that arrangement, I started over, first unzipping, THEN importing from within X. I'd volunteer to update/amend the docs, but I'm not sure what's going on. -- Roy Wilson |