Check Computation Server Window
    The server status window purpose is to show information about the computation server and to manage the running and completed jobs. You can invoke it by using the "Check Remote Server Status" in the OptiLine "File" menu. Use the bottom "Refresh" button to actualize all information. The window is divided into four tabs :
  • Welcome Tab : This tab displays the server welcome message, IP and Port.
  • Status Tab : This tab displays information on the server status
    • Connection (peak) : The maximum number of simultaneous connections
    • Connection (hits) : The number of connection since the server last restart
    • Collector : The number of jobs currently queued and waiting to be computed
    • Finished jobs : The number of jobs already computed and available for download
    • Server Load : This bar graph displays the number of projects currently being computed on the server
    • User queue limit : This number depends on the user account properties and displays the maximum number of jobs a user can queue
    • Lock : This number identifies the server run and is increased each time the server is restarted
    • The three checkboxes (User Can View / Can Delete / Is Administrator) define the current user privileges
    • The two pie-panels display per user and for all users the status of the completed jobs.
        • Finished : The optimization finished successfully
        • Stopped : The optimization was interrupted by the user but a valid result is available
        • Canceled : The jobs were canceled by the user
        • Failed : The algorithm failed to find a valid first solution (Infeasible constraints for example)
        • Crashed : The algorithm crashed
  • Queue Tab : This tab displays information about the jobs in the queue and the jobs currently being computed as a table :
    The priority column displays for each job its priority. Jobs with higher priority will be submitted to the computation engine first. The running column when filled with an icon as showed on the right screenshot, displays if a job is currently computed or waiting to be computed. Depending on your privileges, you can or not have multiple jobs simultaneously in the computation engine. For example, in the left screenshot, paul has two jobs in the queue, but only one is currently optimized. The second one will have to wait the end of the first one. But with a more powerful account, paul could have been able to optimize all his projects simultaneously.
    Depending on your account privileges, you will be able to use some (possibly none) of the three buttons on the top part of the window and will be able to view only yours or all the user jobs.
    • Cancel Job Button : This button will interrupt a currently running job without getting any intermediate result
    • Request Stop Button : This button will ask the algorithm to stop and to send the currently available results in the ready queue
    • Inspect Button : This button lets you visualize the currently optimized project
  • Ready Tab: This tab displays all the finished jobs.
    Depending on your privileges, you will be able to view your jobs or all users jobs by checking the "Display current user jobs only" checkbox. To delete one or multiple results simply select them and hit the "Delete" button. To download a particular result, select it and choose the "Download" button. (Note that only valid results are downloadable).
    The table displays information on each result. The "OK" column can contain one of these three icons :
    • OK icon [] : This icon means that the optimization finished successfully
    • Yellow OK icon [] : This icon means that the optimization was stopped before its end, intermediate result is available for download
    • Cross icon [] : This icon means that this result is not downloadable. Further information comes from the aborted column :
      • An aborted column filled with a icon, means that this job was killed by the user
      • An aborted column filled with a icon, means that this job did not complete successfully. This could be due to various reasons :
        • Infeasible constraints
        • Wrong data format...