Comments (2)
- Pipeline
Do you see it as a grid listing + "add new" interface?
- 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.
- InspectionRun
A display-only grid of "/inspection_runs"?
- 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
- 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?
from pd.
- Pipeline
Do you see it as a grid listing + "add new" interface?
Yes please!
- 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.
- 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.
- 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!
- MatchRunner
Is this a grid of run matches with the "launch" button and job status? Why not add "run" + status to the screen 4.?
-
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>
orrun_matches
- the conf is all included there now. -
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
from pd.
Related Issues (4)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pd.