Note: the JESS Client will be integrated into the DesignBuilder software from version 4. The information below applies only to certain beta versions of DesignBuilder V3 software in which the DB Job Server function is available.
Through the new JobServer function provided in the latest DesignBuilder Beta package, it is possible to send simulation jobs, especially those of the optimisation process, to the JESS server on the DMU cluster. This page describes how to setup the necessary components, and connect to the JESS server.
Some preparation steps have to be taken. These may have already been done, in which case you can move to the next section.
java -version, followed by the Enter key
Once you have downloaded the JESS Client for DB and received a JESS account, you must first perform the following steps to initialize the connection.
EnergyPlusfolder, and then double-click on the Windows Batch File named
Register_Userif extension is hidden)
C:\Users\Yi\AppData\Local\DesignBuilder\JobServer\Jobs. On Windows XP, the folder may be
C:\Documents and Settings\Yi\Local Settings\Application Data\DesignBuilder\JobServer\Jobs. Remember to replace “Yi” with your own user name on the computer. If you cannot find such folder, it may be set to hidden, in which case you can copy and paste the path into the address bar of file explorer
With the current implementation of the DesignBuilder JobServer, there are three parameters that may affect how simulation jobs are executed in parallel. These are in the JobServer settings, Batch settings, and the population size of the Genetic Algorithm.
The screenshot on the right shows the Manage Server window (see here for how to get to it). The “Concurrent jobs” field governs the maximum number of jobs the JobServer can submit to JESS concurrently. Please do NOT set this number higher than 20 in any case, as it may overload your computer and network.
This screenshot shows the “Number of jobs per batch” field in the Batch tab in Optimisation. Since simulation jobs of the optimisation process are submitted the DB JobServer in batches, this number governs how many jobs to be submitted the JobServer's queue in each batch. The optimisation process will not continue until all jobs in the current batch have returned. This number must be equal to or smaller than the population size explained in the next section.
The optimisation algorithm (GA) used in DB progresses in consecutive “batches”, too, although a “batch” here is normally called a generation of solutions. The population size parameter governs the batch size of the GA process. Population size can be adjusted here on this window.
Remote simulation means you are sending your model to the DMU servers via internet. This raises several issues and risks, such as security and cost. So, please read this section carefully.
Firstly, the remote simulation service we are offering is a limited trial, as part of the ADOPT research project. The trial period is from now till the closing date of the DB Competition (28 December). We may offer to extend the trial period till 31 March, 2013. Both the number of jobs you can submit per week, and the simulation time of each job, are capped. Currently, the maximum simulation time of each job is 60 minutes. Models take longer than 60 minutes to execute will fail. The maximum number of jobs you can submit each week will be determined later, depending on the workload of our servers.
This trial is “free”, which means we are not charging you for using the remote simulation service. However, using this service may not be completely cost free to you. Please consider your own cost for internet access, for example. DesignBuilder models may generate large amount of output data, which has to be transferred through the internet. If your ISP charge internet access by the amount of data you use, you must think very carefully before using this service. In any case, we strongly recommend that you select only the monthly and annual output level for optimisation purpose (see screenshot). This will help reduce data traffic.