From 17e005b38ffdc4f1875ee0bccc819ccd9b5a471f Mon Sep 17 00:00:00 2001 From: FiveMovesAhead Date: Tue, 13 Aug 2024 16:00:49 +0800 Subject: [PATCH] Update README to include vector_search. --- tig-benchmarker/README.md | 6 +++--- tig-worker/README.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/tig-benchmarker/README.md b/tig-benchmarker/README.md index 7bf4b684..5cac2ec5 100644 --- a/tig-benchmarker/README.md +++ b/tig-benchmarker/README.md @@ -29,7 +29,7 @@ There are two ways to start the master benchmarker: ALGOS_TO_COMPILE="" # See notes cargo build -p tig-benchmarker --release --no-default-features --features "standalone ${ALGOS_TO_COMPILE}" # edit below line for your own algorithm selection - echo '{"satisfiability":"schnoing","vehicle_routing":"clarke_wright","knapsack":"dynamic"}' > algo_selection.json + echo '{"satisfiability":"schnoing","vehicle_routing":"clarke_wright","knapsack":"dynamic","vector_search":"optimal_ann"}' > algo_selection.json ./target/release/tig-benchmarker
algo_selection.json ``` @@ -38,7 +38,7 @@ There are two ways to start the master benchmarker: ALGOS_TO_COMPILE="" # See notes docker build -f tig-benchmarker/Dockerfile --build-arg features="${ALGOS_TO_COMPILE}" -t tig-benchmarker . # edit below line for your own algorithm selection - echo '{"satisfiability":"schnoing","vehicle_routing":"clarke_wright","knapsack":"dynamic"}' > algo_selection.json + echo '{"satisfiability":"schnoing","vehicle_routing":"clarke_wright","knapsack":"dynamic","vector_search":"optimal_ann"}' > algo_selection.json docker run -it -v $(pwd):/app tig-benchmarker
algo_selection.json ``` @@ -51,7 +51,7 @@ There are two ways to start the master benchmarker: * `ALGOS_TO_COMPILE` is a space separated string of algorithms with format `_`. Example: ``` - ALGOS_TO_COMPILE="satisfiability_schnoing vehicle_routing_clarke_wright knapsack_dynamic" + ALGOS_TO_COMPILE="satisfiability_schnoing vehicle_routing_clarke_wright knapsack_dynamic vector_search_optimal_ann" ``` * Every 10 seconds, the benchmarker reads your json file path and uses the contents to update its algorithm selection. diff --git a/tig-worker/README.md b/tig-worker/README.md index 5cd10574..75468031 100644 --- a/tig-worker/README.md +++ b/tig-worker/README.md @@ -30,7 +30,7 @@ cargo build -p tig-worker --release --features "${ALGOS_TO_COMPILE}" * `ALGOS_TO_COMPILE` is a space separated string of algorithms with format `_`. Example: ``` - ALGOS_TO_COMPILE="satisfiability_schnoing vehicle_routing_clarke_wright knapsack_dynamic" + ALGOS_TO_COMPILE="satisfiability_schnoing vehicle_routing_clarke_wright knapsack_dynamic vector_search_optimal_ann" ``` # Usage