| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Running into when setting up a test through the API with client.validate.create_scenario_test("new baseline test images", slice_id="slc_c81fxadwzftg238jb5zg", evaluation_functions=[client.validate.eval_functions.bbox_iou()]) I guess this is some Pydantic issue, right? |
Sorry, something went wrong.
|
If you have difficulty testing this PR (getting 400 errors), you are probably hitting the production scaleapi server instead of the local feature branch. you would initialize the client like this: client = nucleus.NucleusClient(os.environ.get("API_KEY"), endpoint='http://localhost:3000/v1/nucleus') where on localhost:3000, you have the other feature branch checked out To run pytest against the feature branch, do: export NUCLEUS_ENDPOINT='http://localhost:3000/v1/nucleus in the window where you're running pytest |
Sorry, something went wrong.
|
We also need to update the scenario_test.add_criterion(...) method. I tried st.add_criterion(client.validate.eval_functions.bbox_map()) which doesn't work. Let's also rename it to add_eval_function(...) in order to avoid confusion. |
Sorry, something went wrong.
|
Renamed add_criterion to add_eval_function |
Sorry, something went wrong.
|
Tested locally and interaction with the backend works! My bad, forgot this earlier, let's also rename metric.get_criteria() to metric.get_eval_functions() to make it consistent. |
Sorry, something went wrong.
There was a problem hiding this comment.
let's test after the backend deployed, but lgtm after the rename suggestion
Sorry, something went wrong.
add new set model as baseline functions to client, remove add_criteria in favor of add_eval_function, bump version number and changelog
| Back | FazBrowse Home | New Git URL |
Changes the interface on Scenario Test Creation to not require setting thresholds up front. Instead of passing in a test criteria, a user instead initializes the test with a list of evaluation functions, from which criteria are created with threshold null.
Users can later customize this threshold with metric.set_threshold
This PR also introduces the API interface for setting a model as a baseline for a whole unit test.
Implemented pytest coverage for both.
Shortcut ticket: https://app.shortcut.com/scaleai/story/399936/remove-manual-thresholding-from-api-interface-for-validate
Corresponding scaleapi side PR: https://github.com/scaleapi/scaleapi/pull/37635
Note: build won't pass until scaleapi side is deployed, but we expect pytest to pass when run against those changes locally