Skip to content

Draft template based on new schema#166

Open
Dvermetten wants to merge 1 commit intopush-zmvqzzrwnlupfrom
template_new
Open

Draft template based on new schema#166
Dvermetten wants to merge 1 commit intopush-zmvqzzrwnlupfrom
template_new

Conversation

@Dvermetten
Copy link
Copy Markdown
Contributor

No description provided.

@Dvermetten Dvermetten requested a review from olafmersmann April 21, 2026 12:40
Comment thread template.yaml
max: 5
objectives: # For objectives, also indicate the number, either as an integer, list or range
- 1
constraints: #constraints refers to hard constrains (violations don't have a true fitness value)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we make this distinction I would just call this hard_constraints explicitly, to match with soft_constraints

Comment thread template.yaml
- 1
constraints: #constraints refers to hard constrains (violations don't have a true fitness value)
#Similar to variables, specify for each type of constraints the number, list, or a range.
box: 1
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be nice to have an easy way to say all variables are box constrained

Comment thread template.yaml
max: 5
objectives: # For objectives, also indicate the number, either as an integer, list or range
- 1
constraints: #constraints refers to hard constrains (violations don't have a true fitness value)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How can I specify that constraints are equality or inequality?

Comment thread template.yaml
can_evaluate_objectives_independently: yes / no / some # Can objective functions be evaluated independently of each other yes, no or some
code_examples: null #Link to a code example in the OPL repository
description: lorem ipsum #Textual description of the problem/suite/generator
dynamic_type: null #If the problem is dynamic, specify the type of dynamics. If not, enter null.
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be good to be able to distinguish between an explicit 'no' there are no dynamic properties, and 'unknown' (whoever added it does not know, if someone knows they should update it).

Comment thread template.yaml
dynamic_type: null #If the problem is dynamic, specify the type of dynamics. If not, enter null.
fidelity_levels: 1 #Number of fidelity levels, if applicable. If not, enter 1.
modality: null #list of modalities (e.g. unimodal, multimodal)
noise_type: null #type of noise (e.g. additive, multiplicative, heteroscedastic)
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for dynamic, an explicit no / unknown would be nice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants