U h @sNddlZddlZddlZejddddlmZmZddZedkrJedS) Nz%(levelname)s: %(message)s)format)"check_model_can_use_ort_mobile_pkgusability_checkercCstjdtjd}|jdddtjtd|jddd d d gd d d |jddtjd|}t d}|j dkr| t j n<|j d kr| t jn$|j d kr| t jn | t jtj|jd|d}t|j|j||d|r|dn |ddS)NzAnalyze an ONNX model to determine how well it will work in mobile scenarios, and whether it is likely to be able to use the pre-built ONNX Runtime Mobile Android or iOS package.) descriptionformatter_classz --config_pathzbPath to required operators and types configuration used to build the pre-built ORT mobile package.F)helprequiredtypedefaultz --log_leveldebuginfowarningerrorz Logging level)choicesr r model_pathzPath to ONNX model to check)rr check_usability)Z skip_optimizeloggeraRun `python -m onnxruntime.tools.convert_onnx_models_to_ort ...` to convert the ONNX model to ORT format. By default, the conversion tool will create an ORT format model with saved optimizations which can potentially be applied at runtime (with a .with_runtime_opt.ort file extension) for use with NNAPI or CoreML, and a fully optimized ORT format model (with a .ort file extension) for use with the CPU EP.a As NNAPI or CoreML may provide benefits with this model it is recommended to compare the performance of the .with_runtime_opt.ort model using the NNAPI EP on Android, and the CoreML EP on iOS, against the performance of the .ort model using the CPU EP.zNFor optimal performance the .ort model should be used with the CPU EP. )argparseArgumentParserArgumentDefaultsHelpFormatter add_argumentpathlibPathrZget_default_config_path parse_argslogging getLoggerZ log_levelsetLevelDEBUGINFOWARNINGERRORrZ analyze_modelrZ run_checkZ config_pathr )parserargsrZtry_epsr$W/tmp/pip-unpacked-wheel-socb9apf/onnxruntime/tools/check_onnx_model_mobile_usability.pyrsJ      r__main__) rrr basicConfigZmobile_helpersrrr__name__r$r$r$r%s 4