If you meant reader as in a for .cbr files (e.g., for manga or comics), let me know, and I’ll provide a full write‑up for that use case instead.
OUTPUT: solution_repair_cost | Option | Description | |--------|-------------| | -v , --verbose | Show detailed parsing info, attribute types, and similarity mappings | | -s , --stats | Display dataset statistics: case count, attribute cardinality, missing values | | -q , --query | Run a test query against the case base (requires similarity config) | | -f , --format | Output format: table , json , csv (default: table) | | -k , --top-k | Number of nearest neighbors to retrieve (default: 5) | | -o , --output | Save output to file | | -h , --help | Show help message | 5. Example Usage Basic read $ reader cbr car_diagnosis.cbr Output: reader cbr
Case count: 2 Missing values: 0 Attribute 'brand': unique values [tesla, bmw] Price range: 32000.0 – 45000.0 $ reader cbr car_diagnosis.cbr --query "brand=tesla year=2021 price=40000" Output: If you meant reader as in a for
DOMAIN: car-diagnosis ATTRIBUTES: - brand: symbolic - engine_noise: symbolic - year: integer - price: float - is_electric: boolean CASES: case1: brand=tesla, engine_noise=quiet, year=2022, price=45000.0, is_electric=true case2: brand=bmw, engine_noise=loud, year=2019, price=32000.0, is_electric=false for manga or comics)