Using Image J. Plugin/macro should start from icon. Images being processed will include a visual scale. The visual scale is positioned during capture along the axis of interest (close to vertical) and indicates not only image scale but also origin (although 0,0 is usually not visible in the field of view). Visual scale might, for example, show a ruler at 9" through 12". First user mouse click would be on the 12" mark. User would also enter "12" or accept the default value (previous) by pressing "enter" or right mouse click. Second mouse click would be, again for example, the 10" mark. User would then specify "2" as the scale length between the points selected or accept the default value (previous) by pressing "enter" or right mouse click. Routine must allow zoom tools in and out during user selection process and preferrably utilize zooming via wheel mouse centered on current cursor position (AutoCAD-like operation). The result of user input would be that the running coordinates for X and Y in Image J would indicate the origin and scale calculated from user-selected points instead of pixel count from the lower-left corner of the image which is standard for Image J. In the above example, the first user-selected point would represent ([url removed, login to view], [url removed, login to view]) and second point (x,y) where x and y are calculated based on its distance (in pixels) from first point and scale value provided by user, which in the example was "2". Routine should display coordinates to the third decimal place. Routine should allow image to be saved with user coordinate system attached and allow re-opening at a later time. However, opening new unprocessed image should cause Image J to revert to default coordinate system allowing users to distinguish between previously processed and unprocessed images. Running the routine on a previously processed image should over-write previous data.
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Deliverables must be in ready-to-run condition, as follows (depending on the nature of the deliverables):
a) For web sites or other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).