Developer's corner
From Mallet
Here are some notes that might be useful for people writing Java code that uses Mallet.
- Here's a short overview of the code organization.
- If you use the optimization framework, then a useful test of your code is to see whether your user-supplied gradient agrees with a finite-different gradient taken from your value function. We have a test class that does this. Find out more about TestMaximizable.
- The default Maximizer for gradient ascent in MALLET is LimitedMemoryBFGS. Here's a description of exceptions you may get if something goes wrong during optimization, and what you can do about them (short answer, use TestMaximizable).
Here are some notes which are probably only useful to Mallet committers:
- A short note about how to commit to MALLET.
- Also, make sure you use a consistent code style.
- If you would like to make the base Mallet distribution dependent on a new external library, find out about adding external dependencies.
- See these guidelines for writing unit tests.
[edit]
Development Notes
Here are some notes among the MALLET developers.
- MALLET 0.4 todos
- Things that will be changed in MALLET 2.0.