# Challenge problems¶

## Overview¶

The reliability problems – grouped into different sets – are summarized in the tables below. The sets are established to represent distinctively different problems where different methods are expected to excel, e.g. reliability problems with a single design point, or reliability problems with continuous and differentiable performance function. Sets and problems are identified with their `set_id`

and `problem_id`

, respectively; both are integers.

You can download all of the probabilistic models from the GitLab repository in a tabular format by clicking on this link.

## Problem sets¶

### Tutorial set¶

To help the understanding and verification purposes all details are disclosed for the first two problems in this set. Problem 3 exemplifies what information will be provided during the challenge for each reliability problems. Since these problems serve testing, no upper limit on the number of performance function evaluations is enforced. Use `username: 'testuser'`

and `password: 'testpass'`

for testing (only available for the tutorial).

`username` |
‘testuser’ |

`password` |
‘testpass’ |

`set_id` |
`problem_id` |
Reliability problem | Max evaluations |
---|---|---|---|

-1 | 1 | RP8 | \(\infty\) |

-1 | 2 | RP22 | \(\infty\) |

-1 | 3 | RP33 | \(\infty\) |

### Challenge set 1 - single performance function¶

Reliability problems in this set have a single performance function but nothing else is disclosed about them. Once the challenge is open (Timeline) you can register and use your username and password to access these problems.

Evaluating the performance function yields a component and a system performance function value. These are equal as we have only a single performance function.

Note

Some of the performance functions rely on iterative numerical algorithms which might fail to converge under certain inputs; similarly as a finite element analysis. In those cases NaN values are returned. Make sure that your reliability algorithm can handle these cases. The performance functions will not yield NaN values for reasonable input points that do not correspond to failure.

`set_id` |
`problem_id` |
Reliability problem | Max evaluations |
---|---|---|---|

1 | 1 | RP14 | 10000 |

1 | 2 | RP24 | 10000 |

1 | 3 | RP28 | 10000 |

1 | 4 | RP31 | 10000 |

1 | 5 | RP38 | 10000 |

1 | 6 | RP53 | 10000 |

1 | 7 | RP54 | 10000 |

1 | 8 | RP63 | 10000 |

1 | 9 | RP75 | 10000 |

1 | 10 | RP107 | 10000 |

1 | 11 | RP111 | 10000 |

1 | 12 | RP201 | 10000 |

1 | 13 | RP203 | 10000 |

1 | 14 | RP213 | 10000 |

1 | 15 | RP300 | 10000 |

1 | 16 | RP301 | 10000 |

### Challenge set 2 - Multiple, known number of performance functions¶

Reliability problems in this set have unknown number of performance functions. Once the challenge is open (Timeline) you can register and use your username and password to access these problems.

Evaluating the performance function yields performance function values for each component and the system as well. However, how the system performance function is calculated is not revealed, you test the RP33 system problem from the tutorial set.

Note

Some of the performance functions rely on iterative numerical algorithms which might fail to converge under certain inputs; similarly as a finite element analysis. In those cases NaN values are returned. Make sure that your reliability algorithm can handle these cases.

`set_id` |
`problem_id` |
Reliability problem | Max evaluations |
---|---|---|---|

2 | 1 | RP25 | 10000 |

2 | 2 | RP33 | 10000 |

2 | 3 | RP35 | 10000 |

2 | 4 | RP55 | 10000 |

2 | 5 | RP57 | 10000 |

2 | 6 | RP60 | 10000 |

2 | 7 | RP77 | 10000 |

2 | 8 | RP89 | 10000 |

2 | 9 | RP91 | 10000 |

2 | 10 | RP110 | 10000 |

2 | 11 | RP202 | 10000 |