Estimated runtime of cases

Introduction

On the platform, an estimated runtime is shown when submitting a case (Design or Simulation). This runtime is an estimate from a reference case. The actual time taken to complete a case can vary and is influenced by different factors. After submitting a case, the time taken to complete the case is updated on the platform and typically is unique to the case.

To keep the computation time of your case to a minimum, you can take into account a few factors. Below you can find an overview of the factors that affect the computation time. Please note that the computation times indicated in the table are an estimation and can depend on the complexity of your case. The complexity of your case depends on whether or not your case has a complex geometry, geometry with small features, or regions that significantly differ in size,…

Simulation

The estimated time for a simulation to finish is 1 day for general cases. The table below shows an estimate of different factors that can affect the computation time. Using this as a reference you can estimate the approximate time taken for your case to be completed.

ConceptualDetailed
Baseline credit amount15 credits100 credits
Resolution level
Conceptual1 day
Detailed1 day (see note)
Number of regions
Solid regions1+0 days+0 days
5+0.15 days+0.1 days
10+0.3 days+0.2 days
20+0.6 days+0.4 days
Rule of thumb for more than 1 solid region+0.03 days times the number of solid regions+0.02 days times the number of solid regions
Fluid regions1+0 days+0 days
2+1 day+2 days
3+2 days+4 days
Rule of thumb for more than 1 fluid region+1 day times the number of fluid regions+2 days times the number of fluid regions
Settings
Temperature-dependent material propertiesTotal number of days times 2Total number of days times 2
Buoyance enabledTotal number of days times 2Total number of days times 2
Radiation enabledTotal number of days times 1.8Total number of days times 1.8

📘

Note

Increasing the amount of credits spent on your case will decrease the computational time and vice versa.
For example, if you assign 60 credits to your conceptual simulation case, the total number of days from the table above must be divided by 4. For a detailed simulation, on the other hand, the time to completion will nearly double since 60 is less than the 100 baseline number.

Design

The estimated time for a design to complete is 2 – 4 weeks depending on the resolution level. The table below shows an estimate of different factors that can affect the computation time. Using this as a reference you can estimate the approximate time taken for your case to be completed.

ConceptualDetailed
Baseline credit amount100 credits100 credits
Resolution level
Conceptual16 days
Detailed32 days
Number of regions
Solid regions1+0 days+0 days
2+3 days+1.5 days
3+6 days+3 days
4+9 days+4.5 days
Rule of thumb for more than 1 solid region+3 days times the number of solid regions+1.5 days times the number of solid regions
Fluid regions1+0 days+0 days
2+16 days+32 days
3+32 days+64 days
Rule of thumb for more than 1 fluid region+16 days times the number of fluid regions+32 days times the number of fluid regions
Settings
Temperature-dependent material propertiesTotal number of days times 2Total number of days times 2
Buoyance enabledTotal number of days times 2Total number of days times 2
Radiation enabledTotal number of days times 1.8Total number of days times 1.8

📘

Note

Increasing the amount of credits spent on your case will decrease the computational time and vice versa.
For example, if you assign 200 credits to your conceptual design case, the total number of days from the table above must be divided by 2. The same holds for a detailed design case since both have a 100-credit baseline.

Delivery type

Depending on the number of credits you select for a case, you can assign less or more computational power to the case.

Factors that affect the computational time

  • Type of submission: This refers to the type of design or simulation case that the user chooses to run on the platform.
  • Resolution level: It can be a conceptual or a detailed case. The conceptual case is a low resolution and takes less time than the detailed case which is in high resolution.
  • Number of regions: The number of regions in the geometry uploaded on the platform plays a role in the computation time. While it is easier to include the entire assembly of the case on the platform, it will increase the computation time and is counterproductive. A better approach would be to include the regions that directly influence the case.
  • Number of boundaries: The number of boundaries that are included in the case also affects the time. Like the regions, it is important to include the boundaries that directly influence the case.
  • Number of targets: With generative thermal design, the user can benefit by running an optimization with multiple targets. The time will increase with the number of targets that are included.
  • Buoyancy: Solving for buoyancy means an increased number of iterations of the heat and momentum equations which thereby increases the runtime as well.
  • Radiation: When enabling radiation, the software solves the radiative heat transfer equation (RTE) at every stage of the optimization to ensure accurate results. This complex equation affects the runtime of the case.

🚧

Human errors

This involves errors in parameters and non-physical case setups. This can lead to cases being stalled or increase the runtime making it infeasible.