Recently, I have begun work to provide improved documentation and file releases for users outside of the SeisSpace user base. At the same time, I am also undertaking a major refactoring effort. JavaSeis development has up to this point been driven mainly by the needs of seismic processing as represented by the SeisSpace seismic processing system from Halliburton / Landmark Graphics. As the SeisSpace product has gained more acceptance in the marketplace, we have been hearing more interest in using JavaSeis outside of SeisSpace. These requests have come from seismic software companies, research groups in oil companies, and university consortia that are supported by the oil industry.
As anyone who works in software knows, a good design often is eroded by usage. This has been the case for JavaSeis. Under the pressure of expediency, sub-optimal design choices creep into the system, and a clean design starts to get complicated. The refactoring effort is aimed at cleaning up the JavaSeis code base in preparation for future SeisSpace releases, but is also intended to enable usage of JavaSeis frameworks outside of SeisSpace. The areas that I think need work are:
- Continue to support Eclipse based developement for JavaSeis
- Add support for Thread parallel and mixed MPI / Thread parallel applications
- Investigate OSGi / Equinox for a services model in JavaSeis
- Provide a tool framework and execution environment for JavaSeis applications
- Extract a clean interface for JavaSeis parallel I/O
- Create a plugin architecture for interface implementations
Stay tuned for more updates !
-Chuck
No comments:
Post a Comment