h&`SSKJr SSKrSSKrSrSSKJrJr SS Sjjr g!\a SrNf=f) ) annotationsNT)$GloballyAllowedTypesOpTypeImplFilterOperatorTypeUsageManagerFcR^^^[RRU5(d[SUS35eT=(a [m0nSmT(a [ 5OSnSnSmUUU4Sjn[ U5nUVs/sHowR5PM snGHnU"U5(aMSURS55upn U RS5V s/sHn [U 5PM n n S U ;Ga8S n[5nS n[U 5nUU:GaU RSU5nU RS U5nUS :XaUnS Us=:aU:aO OXUR5nURU5 US -nS nUS :a6UU:a0U US :XaUS - nOU US:XaUS -nUS - nUS :aUU:aM0US :wa[SU US-5eU(aU UUnURU UU5 US -nO0US :waUOUnURXUR55 US -nUU:aGMO/U RS5Vs1sHnUR5iM nnU H7nX;aUU0X)'MUX);a XU U'M!X)UR!U5 M9 GM SSS5 [U5S :Xa T(aSnSnT(a?U(dSnTbUb [S5eTb[#T5nUU4$UbUR%5nUU4$s snfs sn fs snf!,(df  N=f)a Parse the configuration file and return the required operators dictionary and an OpTypeImplFilterInterface instance. Configuration file lines can do the following: 1. specify required operators 2. specify globally allowed types for all operators 3. specify what it means for no required operators to be specified 1. Specifying required operators The basic format for specifying required operators is `domain;opset1,opset2;op1,op2...` e.g. `ai.onnx;11;Add,Cast,Clip,... for a single opset `ai.onnx;11,12;Add,Cast,Clip,... for multiple opsets note: Configuration information is accrued as the file is parsed. If an operator requires support from multiple opsets that can be done with one entry for each opset, or one entry with multiple opsets in it. If the configuration file is generated from ORT format models it may optionally contain JSON for per-operator type reduction. The required types are generally listed per input and/or output of the operator. The type information is in a map, with 'inputs' and 'outputs' keys. The value for 'inputs' or 'outputs' is a map between the index number of the input/output and the required list of types. For example, both the input and output types are relevant to ai.onnx:Cast. Type information for input 0 and output 0 could look like this: `{"inputs": {"0": ["float", "int32_t"]}, "outputs": {"0": ["float", "int64_t"]}}` which is added directly after the operator name in the configuration file. e.g. `ai.onnx;12;Add,Cast{"inputs": {"0": ["float", "int32_t"]}, "outputs": {"0": ["float", "int64_t"]}},Concat` If for example the types of inputs 0 and 1 were important, the entry may look like this (e.g. ai.onnx:Gather): `{"inputs": {"0": ["float", "int32_t"], "1": ["int32_t"]}}` Finally some operators do non-standard things and store their type information under a 'custom' key. ai.onnx.OneHot is an example of this, where the three input types are combined into a triple. `{"custom": [["float", "int64_t", "int64_t"], ["int64_t", "std::string", "int64_t"]]}` 2. Specifying globally allowed types for all operators The format for specifying globally allowed types for all operators is: `!globally_allowed_types;T0,T1,...` Ti should be a C++ scalar type supported by ONNX and ORT. At most one globally allowed types specification is allowed. Specifying per-operator type information and specifying globally allowed types are mutually exclusive - it is an error to specify both. 3. Specify what it means for no required operators to be specified By default, if no required operators are specified, NO operators are required. With the following line, if no required operators are specified, ALL operators are required: `!no_ops_specified_means_all_ops_are_required` :param config_file: Configuration file to parse :param enable_type_reduction: Set to True to use the type information in the config. If False the type information will be ignored. If the flatbuffers module is unavailable type information will be ignored as the type-based filtering has a dependency on the ORT flatbuffers schema. :return: required_ops: Dictionary of domain:opset:[ops] for required operators. If None, all operators are required. op_type_impl_filter: OpTypeImplFilterInterface instance if type reduction is enabled, the flatbuffers module is available, and type reduction information is present. None otherwise. zConfiguration file z does not existFNc8>U(aURS5(agURS5(aWT(aOTb [S5eURS5SRS5Vs1sHoR5iM snmgUS:XaSmgg s snf) N#Tz!globally_allowed_types;z.Globally allowed types were already specified.;r,z,!no_ops_specified_means_all_ops_are_requiredF) startswith RuntimeErrorsplitstrip)linesegmentenable_type_reductionglobally_allowed_types+no_ops_specified_means_all_ops_are_requireds g/var/www/fran/franai/venv/lib/python3.13/site-packages/onnxruntime/tools/reduced_build_config_parser.pyprocess_non_op_line)parse_config..process_non_op_lineasts++ ??5 6 6$)5&'WXXIMTWYZI[IaIabeIf)gIfg--/If)g& A A:> 7*hs0Bc3@# UHoR5v M g7f)N)r).0rs r parse_config..ys/_G sr r {Trr}z#Mismatched { and } in type string: zYSpecifying globally allowed types and per-op type reduction info together is unsupported.)ospathisfile ValueErrorhave_flatbuffersropenrrintsetlenfindaddr restore_from_config_entryupdatermake_op_type_impl_filter) config_filer required_opsop_type_usage_managerhas_op_type_reduction_inforconfig orig_linerdomain opset_str operators_strsopsets operatorscurend next_commanext_open_braceoperatorinum_open_bracestype_strend_stropopsetop_type_impl_filterrrs ` @@r parse_configrEsH 77>>+ & &.{m?KLL2F6FL27/:O46UY!&!& k f8>?9__&?D"4((/_tzzZ]/_ ,F}&/ooc&:;&:c!f&:F;m#-1* E -(Ci!.!3!3C!=J&3&8&8c&BO!R'%( ?7Z7#0_#E#K#K#M! h/,a/*+-1a#g,Q/36 /1 4!.q!1S!8 /1 4FA .1a#g+a/"./TWdeteuWv/v"ww0'4_Q'GH1KKFT\^fg!e1;b0@*c! m&@&F&F&HI%kQCiV3@2E2Ec2JK2JBRXXZ2J K-,19+=L(,"662;(/ (/66yA  {@ L <A"M )$( ! ! -2G2Sk  " -"FG]"^  , ,,# ."7"P"P"R  , ,,m@ rNs;# ` z- s "--