Use updated format for input models

[j2whiting]

We need to account for 3 different forms of parameter matrices to reduce ambiguity in configuration pipelines:

• subject/outcome
• subject/controller
• outcome/controller

Update output from HMI and the GoLLM prompts with few shot examples.

[j2whiting]

We have a first pass for this data structure, but there are duplicate triplets which are problematic for the downstream configuration tasks.

TODO:

• [ ] Provide step-by-step instructions for how a human would resolve ambiguous parameter values using this new data structure, an AMR and an interaction matrix

Data Structure Sample

[
  {
    "id": "N",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "d",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "c",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "e",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "f_0",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "f_1",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_2"
    ]
  },
  {
    "id": "f_2",
    "subject": "S_1",
    "outcome": "E_1",
    "controllers": [
      "I_3"
    ]
  },
  {
    "id": "f_3",
    "subject": "S_2",
    "outcome": "E_2",
    "controllers": [
      "I_2"
    ]
  },
  {
    "id": "f_4",
    "subject": "S_2",
    "outcome": "E_2",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "f_5",
    "subject": "S_2",
    "outcome": "E_2",
    "controllers": [
      "I_3"
    ]
  },
  {
    "id": "f_6",
    "subject": "S_3",
    "outcome": "E_3",
    "controllers": [
      "I_3"
    ]
  },
  {
    "id": "f_7",
    "subject": "S_3",
    "outcome": "E_3",
    "controllers": [
      "I_1"
    ]
  },
  {
    "id": "f_8",
    "subject": "S_3",
    "outcome": "E_3",
    "controllers": [
      "I_2"
    ]
  },
  {
    "id": "a",
    "subject": "E_1",
    "outcome": "I_1",
    "controllers": []
  },
  {
    "id": "b",
    "subject": "I_1",
    "outcome": "R_1",
    "controllers": []
  }
]

[j2whiting]

AMR strings sent to GoLLM from HMI will now contain mapping metadata which will be formatted into the prompt.

The dataset -> config chain prompt has been updated on the GoLLM side to utilize the metadata.

[j2whiting]

@mwdchang is this ready to be closed as complete?