Not ACT-R 6.1, but 7. While I've got a bunch of opinions about ditching chunktypes, I am fully committed to supporting it in jACT-R. In fact, the majority of the declarative system works with or without chunktype specifications. The problem is that chunktypes provided a very natural and efficient way to segment the data space, supporting many of the optimizations within jACT-R.

Inputs into modules...

An interesting question came up today at the ACT-R workshop. I was asked if I had a diagram of all the inputs and outputs of the various modules. It threw me off because the inputs and outputs of a module are going to be dictated by the design of that particular module*.

Version 2 is released.

The newest version of jACT-R and its supporting tools has been released. It is recommended that you do a clean install.

This update includes:

Some thoughts on performance & time synchronization.

In preparation for the 2015 ACT-R workshop, I've been working with my boss on an interesting model. What makes it interesting is that it runs full throttle for about 30 minutes of interactions, followed by a day of rest, for almost a full year. It's a model that actually does quite a bit of work, has massive numbers of references, and is very long lived. My boss built the initial model. I then took it and did an almost 1:1 conversion to jACT-R. It's provided some interesting comparisons, insights, and new optimizations.

Road to 2.0

This website doesn't see nearly as much activity as the development of jACT-R itself. In the past two years there has been much work in decoupling of components, optimizations, new features, and bug fixes. Some of changes have been intended, but not implemented for backward compatibility. For the past 10 years, jACT-R has puttered along relying upon Java1.5. 1.8 finally introduces lambdas and much better concurrency constructs. It's time to make the change.

Define 'eminent'..

Ok, I admit it. I am horrible at keeping this site updated. There has been significant and continued progress behind the scenes. If you use the auto-update feature, you should have seen all the changes.

In the past few months it has become clear that a new version is overly due. This will include some major refactoring - but most code shouldn't be affected. Details are forth coming.

Update eminent

Yes, development is still on going and active!

In the next week or so, a new version will be released that supports three huge chunks of new functionality: multiple inheritance (for chunktypes), logical conditionals on the left-hand-side of productions, and production compilation.

All of this comes from the work of Dr. Laura Hiatt. She and I are working together on not only very large memories, but conceptual reorganization and learning across the lifetime.

End of Summer Release

It's the end of the summer and we've got a great big old release for y'all. It includes a slew of bug fixes, some API changes (sorry), new features, and some new IDE fun. This new release does require Eclipse 3.6 (the core doesn't, but the IDE does), but that brings with it an easier installation (see below)


New Tools!

The IDE has had some odd behaviors for awhile now. After watching a coworker struggle a bit with it, I decided to address a few of these issues in my off time.

Most important is the new runtime perspective (which can be launched automatically during runs)


API changes

To maximize code reuse and minimize incompatibility, I work hard to ensure that the APIs rarely change. The core API has been fairly stable for some years now, but has finally required a bit of tinkering.


Subscribe to jACT-R RSS