Recent changes to UI_Functionality_Support

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:34:28 -0000

--- v5 
+++ v6 
@@ -1,49 +1,47 @@
 User Functionality:
-
+===================
 This document describes the tssDAS lead server functionality. Since this is an infrastructure, it has a rather simple functionality. It is designed mainly to, upload, remove the necessary files, Start, stop algorithm, get result, present data.
 
 Upload:
-
+------
 The user will be able to upload a single zip file. The structure of that Zip should be:
 
- a. Trio.xml - described in the following doc [Trio_Xml].
- b. Divider.jar – the jar file containing all the user classes of the Divider.
- c. Assembler.jar - the jar file containing all the user classes of the Assembler.
- d. Algorithem.jar – the jar file that will be distributed for processing. 
- e. ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its     execution. 
+ 1. Trio.xml - described in the following doc [Trio_Xml].
+ 2. Divider.jar – the jar file containing all the user classes of the Divider.
+ 3. Assembler.jar - the jar file containing all the user classes of the Assembler.
+ 4. Algorithem.jar – the jar file that will be distributed for processing. 
+ 5. ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution. 
  
 This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is installed properly.
 
 Remove: 
-
+-------
 This will unregister a specific trio and all the files will be removed. The fine tuning of the folder will be out of the scope of our software as it is not intended to provide access to machines. Please use any external tool of your liking. You will be able to get the folder path.
 
 Start:
-
+------
 The ability to navigate on installed algorithms and start one of them. Please note that the system supports just one algorithm at a time for now. It may support running a few algorithms. 
 
 Stop:
-
+-----
 Choosing to stop an algorithm will be dome by one of the following options:
 
 1. User initiative.
 2. Divider or assembler asks to terminate.
 3. Both dividing and assembling is done.
 
 Get result: 
-
+----------
 Get the result of the of any algorithm stop. This also includes logs for debugging. 
 
 Show Details:
 
 Will show the meta-data defined in the algorithm installation.
 
-Future: 
-
+Future:
+-------
 While developing you always see to the future. Because we can't achieve everything in the future we would like to keep tracks of ideas. We have the following ideas:
     1. Keeping statistical information of an algorithm run
     2. Running parallel algorithms at once.
     3. Running parallel worker stations at once.
     4. securing the connection.
-
-

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:31:41 -0000

--- v4 
+++ v5 
@@ -6,39 +6,44 @@
 
 The user will be able to upload a single zip file. The structure of that Zip should be:
 
- Trio.xml - described in the following doc [Trio_Xml].
- Divider.jar – the jar file containing all the user classes of the Divider.
- Assembler.jar - the jar file containing all the user classes of the Assembler.
- Algorithem.jar – the jar file that will be distributed for processing. 
- ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution. 
-
-This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is installed properly 
-
+ a. Trio.xml - described in the following doc [Trio_Xml].
+ b. Divider.jar – the jar file containing all the user classes of the Divider.
+ c. Assembler.jar - the jar file containing all the user classes of the Assembler.
+ d. Algorithem.jar – the jar file that will be distributed for processing. 
+ e. ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its     execution. 
+ 
+This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is installed properly.
+
 Remove: 
 
 This will unregister a specific trio and all the files will be removed. The fine tuning of the folder will be out of the scope of our software as it is not intended to provide access to machines. Please use any external tool of your liking. You will be able to get the folder path.
 
 Start:
 
 The ability to navigate on installed algorithms and start one of them. Please note that the system supports just one algorithm at a time for now. It may support running a few algorithms. 
 
 Stop:
 
 Choosing to stop an algorithm will be dome by one of the following options:
 
-# User initiative.
-# Divider or assembler asks to terminate.
-# Both dividing and assembling is done.
+1. User initiative.
+2. Divider or assembler asks to terminate.
+3. Both dividing and assembling is done.
 
 Get result: 
 
 Get the result of the of any algorithm stop. This also includes logs for debugging. 
 
 Show Details:
 
 Will show the meta-data defined in the algorithm installation.
 
- Future: 
-
-While developing you always see to the future. Because 
+Future: 
+
+While developing you always see to the future. Because we can't achieve everything in the future we would like to keep tracks of ideas. We have the following ideas:
+    1. Keeping statistical information of an algorithm run
+    2. Running parallel algorithms at once.
+    3. Running parallel worker stations at once.
+    4. securing the connection.
+

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:10:39 -0000

--- v3 
+++ v4 
@@ -6,11 +6,11 @@
 
 The user will be able to upload a single zip file. The structure of that Zip should be:
 
-# Trio.xml - described in the following doc [Trio_Xml].
-# Divider.jar – the jar file containing all the user classes of the Divider.
-# Assembler.jar - the jar file containing all the user classes of the Assembler.
-# Algorithem.jar – the jar file that will be distributed for processing. 
-# ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution. 
+ Trio.xml - described in the following doc [Trio_Xml].
+ Divider.jar – the jar file containing all the user classes of the Divider.
+ Assembler.jar - the jar file containing all the user classes of the Assembler.
+ Algorithem.jar – the jar file that will be distributed for processing. 
+ ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution. 
 
 This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is installed properly

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:09:11 -0000

--- v2 
+++ v3 
@@ -1,645 +1,44 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-User Functionality:
-
-This document describes the tssDAS
-lead server functionality. Since this is an infrastructure, it has a rather
-simple functionality. It is designed mainly to, upload, remove the necessary files,
-Start, stop algorithm, get result, present data.
-
-Upload:
-
-The user will be able to upload a single zip file. The structure
-of that Zip should be:
-
-1.      
-Trio.xml - described in the
-following doc [Trio_Xml].
-
-2.      
-Divider.jar – the jar file
-containing all the user classes of the Divider.
-
-3.      
-Assembler.jar - the jar
-file containing all the user classes of the Assembler.
-
-4.      
-Algorithem.jar – the jar
-file that will be distributed for processing. 
-
-5.      
-ADRF folder – Assembler Divider
-Resource folder, will hold external files the assembler or divider might need
-for its execution. 
-
-This zip will be uploaded to the server unzipped then the
-trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is
-installed properly 
-
-Remove: 
-
-This will unregister a specific trio and all the files will
-be removed. The fine tuning of the folder will be out of the scope of our
-software as it is not intended to provide access to machines. Please use any
-external tool of your liking. You will be able to get the folder path.
-
-Start:
-
-The ability to navigate on installed algorithms and start
-one of them. Please note that the system supports just one algorithm at a time
-for now. It may support running a few algorithms. 
-
-Stop:
-
-Choosing to stop an algorithm will be dome by one of the
-following options:
-
-1.      
-User initiative.
-
-2.      
-Divider or assembler asks
-to terminate.
-
-3.      
-Both dividing and
-assembling is done.
-Get
-result: 
-Get the result of the of any algorithm stop. This also
-includes logs for debugging. 
-

- 
-Show Details:
-Will show the meta-data defined in the algorithm
-installation.
- Future: 
-While developing you always see to the future. Because 
-
-
-
+User Functionality:
+
+This document describes the tssDAS lead server functionality. Since this is an infrastructure, it has a rather simple functionality. It is designed mainly to, upload, remove the necessary files, Start, stop algorithm, get result, present data.
+
+Upload:
+
+The user will be able to upload a single zip file. The structure of that Zip should be:
+
+# Trio.xml - described in the following doc [Trio_Xml].
+# Divider.jar – the jar file containing all the user classes of the Divider.
+# Assembler.jar - the jar file containing all the user classes of the Assembler.
+# Algorithem.jar – the jar file that will be distributed for processing. 
+# ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution. 
+
+This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is installed properly 
+
+Remove: 
+
+This will unregister a specific trio and all the files will be removed. The fine tuning of the folder will be out of the scope of our software as it is not intended to provide access to machines. Please use any external tool of your liking. You will be able to get the folder path.
+
+Start:
+
+The ability to navigate on installed algorithms and start one of them. Please note that the system supports just one algorithm at a time for now. It may support running a few algorithms. 
+
+Stop:
+
+Choosing to stop an algorithm will be dome by one of the following options:
+
+# User initiative.
+# Divider or assembler asks to terminate.
+# Both dividing and assembling is done.
+
+Get result: 
+
+Get the result of the of any algorithm stop. This also includes logs for debugging. 
+
+Show Details:
+
+Will show the meta-data defined in the algorithm installation.
+
+ Future: 
+
+While developing you always see to the future. Because 
+

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:05:10 -0000

--- v1 
+++ v2 
@@ -1,352 +1,346 @@
-
-
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 User Functionality:
 
 This document describes the tssDAS
 lead server functionality. Since this is an infrastructure, it has a rather
 simple functionality. It is designed mainly to, upload, remove the necessary files,
 Start, stop algorithm, get result, present data.
 
 Upload:
 
 The user will be able to upload a single zip file. The structure
 of that Zip should be:
 
 1.      
 Trio.xml - described in the
 following doc [Trio_Xml].
 
 2.      
 Divider.jar – the jar file
 containing all the user classes of the Divider.
 
 3.      
 Assembler.jar - the jar
 file containing all the user classes of the Assembler.
 
 4.      
 Algorithem.jar – the jar
 file that will be distributed for processing. 
 
 5.      
 ADRF folder – Assembler Divider
 Resource folder, will hold external files the assembler or divider might need
 for its execution. 
 
 This zip will be uploaded to the server unzipped then the
 trio.xml file will be parsed for the setup of the algorithm.  There will be a check if the algorithm is
 installed properly 
 
 Remove: 
 
 This will unregister a specific trio and all the files will
 be removed. The fine tuning of the folder will be out of the scope of our
 software as it is not intended to provide access to machines. Please use any
 external tool of your liking. You will be able to get the folder path.
 
 Start:
 
 The ability to navigate on installed algorithms and start
 one of them. Please note that the system supports just one algorithm at a time
 for now. It may support running a few algorithms. 
 
 Stop:
 
 Choosing to stop an algorithm will be dome by one of the
 following options:
 
 1.      
 User initiative.
 
 2.      
 Divider or assembler asks
 to terminate.
 
 3.      
 Both dividing and
 assembling is done.
-
 Get
 result: 
-
 Get the result of the of any algorithm stop. This also
 includes logs for debugging. 
-
 

-
-
+page-break-before:always'>
  
-
 Show Details:
-
 Will show the meta-data defined in the algorithm
 installation.
-
  Future: 
-
 While developing you always see to the future. Because 
-
 
-
 
-

WikiPage UI_Functionality_Support modified by Doron Tsur

Doron Tsur — Sat, 10 Dec 2011 15:03:32 -0000

User Functionality:

This document describes the tssDAS lead server functionality. Since this is an infrastructure, it has a rather simple functionality. It is designed mainly to, upload, remove the necessary files, Start, stop algorithm, get result, present data.

Upload:

The user will be able to upload a single zip file. The structure of that Zip should be:

1. Trio.xml - described in the following doc [Trio_Xml].

2. Divider.jar – the jar file containing all the user classes of the Divider.

3. Assembler.jar - the jar file containing all the user classes of the Assembler.

4. Algorithem.jar – the jar file that will be distributed for processing.

5. ADRF folder – Assembler Divider Resource folder, will hold external files the assembler or divider might need for its execution.

This zip will be uploaded to the server unzipped then the trio.xml file will be parsed for the setup of the algorithm. There will be a check if the algorithm is installed properly

Remove:

This will unregister a specific trio and all the files will be removed. The fine tuning of the folder will be out of the scope of our software as it is not intended to provide access to machines. Please use any external tool of your liking. You will be able to get the folder path.

Start:

The ability to navigate on installed algorithms and start one of them. Please note that the system supports just one algorithm at a time for now. It may support running a few algorithms.

Stop:

Choosing to stop an algorithm will be dome by one of the following options:

1. User initiative.

2. Divider or assembler asks to terminate.

3. Both dividing and assembling is done.

Get result:

Get the result of the of any algorithm stop. This also includes logs for debugging.

Show Details:

Will show the meta-data defined in the algorithm installation.

Future:

While developing you always see to the future. Because