NLM Home Page VHP Home Page

Up: Title Page Index: Full text index Contents: Conference Page 

Image Index

 

fig.1

 [Use Back to navigate] Figure 1. LOF(Library Object Framework) and SPIDER(Subroutine Package for Image Data Enhancement and Recognition).
The first object in the stream with a large downward arrow on its face (LOF_DBfetch) fetches data from the database using EOF and SQL in the background. The second object (LOF_Browser) browses the data from the upper stream and chooses one of them. LOF_ImageViewer connected to LOF_Browser shows an image selected at LOF_Browser. The third object in the stream (ROF_Color2BW) converts image data from the upper stream into a monochrome (black and white) image. The color element, of which intensity constitutes a monochrome image, is presented on ROF_Color2BW. The monochrome image is displayed on LOF_ImageViewer connected to ROF_Color2BW. The fourth objects in the stream (ROF_EGKS1,ROF_EGPR,ROF_EGFC) represents edge-detection algorithms in SPIDER. Each object means a different algorithm. The processed images with ROF_EGKS1,ROF_EGPR, and ROF_EGFC are shown on ROF_ImageViewers connected to the respective objects.
 

fig.2

  Figure 2. LOF(Library Object Framework) and ROF(Research Object Framework).
The first object in the stream with a large downward arrow on its face (LOF_DBfetch) fetches data from the database using EOF and SQL in the background. The second object (LOF_Browser) browses the data from the upper stream and chooses one of them. LOF_ImageViewer connected to LOF_Browser shows an image selected at LOF_Browser. The third object in the stream (ROF_Affin2D) performs Affin transformation, detailed configuration of which is shown in the right side (Configuration Panel). The fourth object (LOF_ImageViewer) connected to ROF_Affin2D reveals an image processed by ROF_Affin2D.
 

fig.3

 [Use Back to navigate] Figure 3. IOF(Internet Object Framework).
The objects with letters of "Login Server","Server1","Server2" on their faces (LOF_DoEntry) are objects that receives a user's input from a browser and converts it into a message EUC objects can understand. The object connected to "Login Server" (IOF_Login) checks user ID/password and returns its result back to "Login Server". The object conncted to "Server1" (IOF_ShowTextForm) makes HTML output that requests a user to input keywords he/she wants to search. The object connected to "Server 2", (IOF_demo1.dcf) is a iconified application, de-iconified version of which is shown in Figure 6.
 

fig.4

  Figure 4. Login via WWW.
This is a screenshot of a browser when IOF_Login in Figure.3 is executed, which shows the first image a user encounters when he/she accesses an the IOF demonstration relevant Web page. In this page, the user puts user ID/password and clicks Login button.
 

fig.5

  Figure 5. Query via WWW.
This is a query page a user sees after he/she succeeds in the login procedure. In this page, the user enters a keyword he/she likes and let the application search for it.
 

fig.6

 [Use Back to navigate] Figure 6. Embedded Application.
This is a fully-unfolded display of IOF_demo1.dcf in Figure.3. The object with a large downward arrow on its face (LOF_DBfetch) fetches data from the database using EOF and SQL in the background. The second object connected in the down stream (LOF_SetDataContents) converts the raw data from the upper stream into formats that a general Web browser can understand (e.g. image format conversion like TIFF to JPEG). The third object (IOF_SetFormat) defines HTML format and makes HTML output with the data from the upper stream embedded.
 

fig.7

  Figure 7. Search Result through IOF.
This is one of the result of IOF application in Figure.3. The result has a form of a table, showing pairs of keys and values.

Up: Title Page Index: Full text index Contents: Conference Page