Problem specification component

[HolographicTripwire]

There should be three blocks to the problem specification component:

• GPT: A text field, which allows the user to type the problem in plaintext
• Table: A html table with toggles which allows the user to set constraints, and specify the optimisation parameters of the problem through a clean table
• Code: A text field in which a problem specification can be written, in our domain-specific language.

The following conversions between the blocks should be implemented:

• The GPT field should provide a button, which can be pressed to produce an API call that updates the Code block.
• Updating either the Code or Table block should automatically update the values in the other accordingly.

[willwill2will54]

The table I would imagine looks something like this:

Contraint	Op	Value	Comment
X + 3Y	>=	3	Some explanation
Z + Y	=	4	More Text
X	>	0	Jibber Jabber

Objective Function

X + Y + 2Z must be maximised