Difference between revisions of "Jeffk-log"
Jump to navigation
Jump to search
Line 18: | Line 18: | ||
** Is completely in Java, a language that I don't know | ** Is completely in Java, a language that I don't know | ||
** Is not oriented towards batch processing as much as ImageMagick | ** Is not oriented towards batch processing as much as ImageMagick | ||
+ | |||
+ | == November 3 == | ||
+ | * Emailed the authors of the paper that I will be basing my project on to see if they can provide me with the code of their system for the software portion of the project. | ||
+ | * Created my project page. |
Revision as of 21:08, 3 November 2007
October 29
I have been considering two possible image handling frameworks for the software portion of my project: ImageMagick and ImageJ. Both seem to have very well documented APIs and modular structures. I have installed ImageMagick from source in my home directory on quark, and I have ImageJ on my own machine. (My machine has an old version of ImageMagick on it as it turns out.) I will be trying-out these two frameworks to see which one best fits my project.
- Pros:
- Is oriented towards batch processing
- Can be used with many languages through different APIs
- Could be faster than ImageJ
- Cons:
- Does not seem to have as many scientific analysis modules as ImageJ
- Pros:
- Has many analysis plugins that are very much like the kinds of things that I will need to be doing
- I have played with this program a little and it has some interesting transforms
- Plugin code can be moved across platforms easily
- Cons:
- Is completely in Java, a language that I don't know
- Is not oriented towards batch processing as much as ImageMagick
November 3
- Emailed the authors of the paper that I will be basing my project on to see if they can provide me with the code of their system for the software portion of the project.
- Created my project page.