You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My partner and I are making a contribution to an open source project for one of our projects and one of the professors recommendations was OpenMDAO. We are wondering what kind of contributions are welcome to make for first time contributors. We compiled a list of issues we wanted to make an attempt at tackling as well:
Task 1: Input report web page has some errors Task Link: [2] Description of Task: The task is to remove the errors shown in the browser console log when viewing the inputs in an HTML file. The error displayed is an Uncaught TypeError, specifically Cannot read properties of null (reading ‘offsetWidth’) and cell.getData is not a function.
Task 2: Implementation of POEM 096: Minimization of Constraint Violation Task Link: [3] Description of Task: The task proposes introducing a capability to minimize constraint violations from a specified starting point of a driver. While SNOPT currently supports finding a feasible starting point, this feature is lacking in other optimizers. This would be implemented by replacing the user-defined objective with one that measures the norm of constraint violations. However, since this new objective isn't directly derived from an OpenMDAO component, reverse mode derivatives would need manual implementation.
Task 3: Add ability to make constraint bounds inputs in SubproblemComp Task Link: [4] Description of Task: It is desired for SubproblemComp to be run under the DOEDriver, with a potential use case to perform a parametric sweep where a constraint bound is gradually increased or decreased across the sweep. To facilitate this, we need the ability to make a constraint bound (lower, upper, or equals) an input of the SubproblemComp.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
My partner and I are making a contribution to an open source project for one of our projects and one of the professors recommendations was OpenMDAO. We are wondering what kind of contributions are welcome to make for first time contributors. We compiled a list of issues we wanted to make an attempt at tackling as well:
Task 1: Input report web page has some errors Task Link: [2] Description of Task: The task is to remove the errors shown in the browser console log when viewing the inputs in an HTML file. The error displayed is an Uncaught TypeError, specifically Cannot read properties of null (reading ‘offsetWidth’) and cell.getData is not a function.
Task 2: Implementation of POEM 096: Minimization of Constraint Violation Task Link: [3] Description of Task: The task proposes introducing a capability to minimize constraint violations from a specified starting point of a driver. While SNOPT currently supports finding a feasible starting point, this feature is lacking in other optimizers. This would be implemented by replacing the user-defined objective with one that measures the norm of constraint violations. However, since this new objective isn't directly derived from an OpenMDAO component, reverse mode derivatives would need manual implementation.
Task 3: Add ability to make constraint bounds inputs in SubproblemComp Task Link: [4] Description of Task: It is desired for SubproblemComp to be run under the DOEDriver, with a potential use case to perform a parametric sweep where a constraint bound is gradually increased or decreased across the sweep. To facilitate this, we need the ability to make a constraint bound (lower, upper, or equals) an input of the SubproblemComp.
Beta Was this translation helpful? Give feedback.
All reactions