Match runner overview

[devonwalshe]

Match runner overview

[sheinin]

1. Pipeline

Do you see it as a grid listing + "add new" interface?

2. RawFile

Sounds like one screen with two identical input sections for files 1 and 2, and the submit button that sends two separate POST requests.

3. InspectionRun

A display-only grid of "/inspection_runs"?

4. RunMatch

I understand that this is our main interface, that now opens with the button "New" and the grid, will have an input form as described:

A POST to RunMatch requires just a name, run_a (earlier InspectionRun), run_b (later InspectionRun), and a pipeline_id

5. MatchRunner

Is this a grid of run matches with the "launch" button and job status? Why not add "run" + status to the screen 4.?

I've added some narrative info to the GET /run_match/1 endpoint

Is it used in the UI?

[devonwalshe]

1. Pipeline
   Do you see it as a grid listing + "add new" interface?

Yes please!

2. RawFile

Sounds like one screen with two identical input sections for files 1 and 2, and the submit button that sends two separate POST requests.
Yes with one page, but we also need to POST the other form data for each raw file, which I've discussed above.

3. InspectionRun
   A display-only grid of "/inspection_runs"?

I was putting it above for reference, not for frontend implementation - the users don't need to see this for now. However you need the ID of the 2 inspection runs (run_a, run_b) in order to create the run_match as you mentioned below.

4. RunMatch

I understand that this is our main interface, that now opens with the button "New" and the grid, will have an input form as described:
A POST to RunMatch requires just a name, run_a (earlier InspectionRun), run_b (later InspectionRun), and a pipeline_id

Precisely!

5. MatchRunner
   Is this a grid of run matches with the "launch" button and job status? Why not add "run" + status to the screen 4.?

1. The runmatch matching launch should take place on the page after you upload the rawfiles - where we currently have the configuration form. The default data for the configuration form should be pulled from the run_match/<id> or run_matches - the conf is all included there now.

2. The best place to launch the export I think is in the grid panel for the run match listings - just add a button to it saying "export data"

I've added some narrative info to the GET /run_match/1 endpoint

Is it used in the UI?

I think you can use the pipe_section_count and sections_checked datapoints