You are here

Best Practices

jACT-R modeling and development will usually go smoothest if you follow some of these best practices. No one size will fit all, but these are some basic foundations that we've found to be the most useful.



  • Name your projects using the java package reverse-URL convention (e.g., org.jactr.core). You can provide a human readable name later, but for the top level use this convention. It makes tracking origin much easier, but has deeper JVM/OSGi consequences.
  • Do not copy projects like templates. There is a large amount of hidden meta information that can be confused.
  • Separate your experiments, modules, extension, and models into separate projects. This helps readability, testing, and makes reusability dramatically easier.