Changes between Version 9 and Version 10 of Documentation/Howto/UseHiveForOptimization

Timestamp:

06/27/11 16:35:24 (13 years ago)

Author:

cneumuel

Comment:

--

Documentation/Howto/UseHiveForOptimization

@@ -20 +20 @@
  1. Each algorithm (also experiments and batch-runs) represent one job. \\ [[Image(JobConfiguration.png, width=800)]] \\
  1. Important configurations are:
-  * CoresNeeded: (default: 1) Specifies how many cores will be reserved for this job on the executing machine. If you know the algorithm corresponding to this job will use multiple threads for computation, increase this number!
-  * MemoryNeeded: (default: 0) Specifies how much memory will be reserved for this job on the executing machine. It will only deployed on machines where the specified amount of memory is available.
+  * !CoresNeeded: (default: 1) Specifies how many cores will be reserved for this job on the executing machine. If you know the algorithm corresponding to this job will use multiple threads for computation, increase this number!
+  * !MemoryNeeded: (default: 0) Specifies how much memory will be reserved for this job on the executing machine. It will only deployed on machines where the specified amount of memory is available.
   * Priority: (default: 0) This number affects the scheduling of the jobs. Higher numbers will be executed earlier. It is recommended to rank jobs with long execution-times to be executed earlier to avoid waiting for them in the end.
-  * ComputeInParallel: This flag is only available for experiments and batch-runs.
+  * !ComputeInParallel: This flag is only available for experiments and batch-runs.
    * Experiment: (default: true) If true, a job will be created for each child-optimizer. If false the whole experiment will be executed as one job.
-   * BatchRun: (default: false) If true, a number of jobs will be created corresponding to the number of repetitions specified. If false the batch-run will be executed as one job.
+   * !BatchRun: (default: false) If true, a number of jobs will be created corresponding to the number of repetitions specified. If false the batch-run will be executed as one job.
  1. There are also some configurations available for the whole experiment:
-   * ResourceIds: You can specify on which machines your jobs should be executed. Those machines/resources are grouped into resource-groups. The top group is ''"HEAL"''. You can either enter the name of a group or the name of a specific machine.
-   * !IsPrivileged: Jobs on Hive are executed in a secure sandboxed appdomain. However some plugins might require elevated privileges. If !IsPrivileged is checked, the jobs will be executed in a unrestricted appdomain. This option is only enabled if the user is allowed to (there is a role called ''"Hive IsAllowedPrivileged"''). If you need this permission, please contact S. Wagner.
+   * !ResourceIds: You can specify on which machines your jobs should be executed. Those machines/resources are grouped into resource-groups. The top group is ''"HEAL"''. You can either enter the name of a group or the name of a specific machine.
+   * !IsPrivileged: Jobs on Hive are executed in a secure sandboxed appdomain. However some plugins might require elevated privileges. If !IsPrivileged is checked, the jobs will be executed in a unrestricted appdomain. This option is only enabled if the user is allowed to (there is a role called ''"Hive !IsAllowedPrivileged"''). If you need this permission, please contact S. Wagner.
  1. After configuring the experiment you can hit ''"Start Experiment"'' and the jobs will be uploaded to the Hive. Hive will then take care of the distribution and execution of each job.
  1. While you keep the Hive Experiment Manager open, it will periodically fetch the status-updates of all jobs. When jobs are finished it will download the results automatically.
  1. You can also close HeuristicLab after uploading an ''Hive Experiment''. When you open the ''Hive Experiment Manager'' again, it will download you list of ''Hive Experiments'' and you can choose to download a specific one.
- 1. Notice that when results are downloaded they will be reassembled into the original experiment. So after it finished you can again open the original experiment (''"Open Experiment"'') and see all the results in the RunCollection as if it would have been executed locally.
-  * Unfortunately it is not possible to preserve the ''ResultsCollection'' of each algorithm when reassembling the experiment. However each ''ResultsCollection'' is stored in the ''RunsCollection'' anyway.
+ 1. Notice that when results are downloaded they will be reassembled into the original experiment. So after it finished you can again open the original experiment (''"Open Experiment"'') and see all the results in the !RunCollection as if it would have been executed locally.
+  * Unfortunately it is not possible to preserve the ''!ResultsCollection'' of each algorithm when reassembling the experiment. However each ''!ResultsCollection'' is stored in the ''!RunsCollection'' anyway.
 
 == Plugins ==
@@ -57 +57 @@
 
 == Merging configuration files ==
-If you are building the trunk or your own HL-solution, the build-process will most likely overwrite ''"HeuristicLab 3.3.exe.config"'' in the target folder. This will overwrite all the Hive-specific configuration. To avoid this, you can use the ConfigMerger to merge the Hive-specific configurations in your own build-process:
+If you are building the trunk or your own HL-solution, the build-process will most likely overwrite ''"HeuristicLab 3.3.exe.config"'' in the target folder. This will overwrite all the Hive-specific configuration. To avoid this, you can use the !ConfigMerger to merge the Hive-specific configurations in your own build-process:
 
- 1. Download config for HiveExperimentManager (source:/branches/HeuristicLab.Hive-3.4/sources/HeuristicLab.Clients.Hive/3.4/ExperimentManagerOnly.config?format=txt)
+ 1. Download config for !HiveExperimentManager (source:/branches/HeuristicLab.Hive-3.4/sources/HeuristicLab.Clients.Hive/3.4/ExperimentManagerOnly.config?format=txt)
  1. Copy the file to your own solution and rename it to ''"HeuristicLab.Hive.config"''
  1. Open properties of the file in Visual Studio and select ''"Copy if newer"'' under ''"Copy to Output Directory"''.
- 1. Add the following line to your ''"MergeConfigs.cmd"'' (if you have one, otherwise specify directly in post-build events):
+ 1. Add the following line to your ''"!MergeConfigs.cmd"'' (if you have one, otherwise specify directly in post-build events):
   * {{{ConfigMerger "%SolutionDir%\HeuristicLab\3.3\%Outdir%\HeuristicLab.Hive.config" "HeuristicLab 3.3.exe.config"}}}