,hC5/SQrSSKrSSKJr SSKJrJr SSKJ r SSK J r SSK J r Jr SSKJrJrJr \(aSSKrS rSS jrSS jrS r0SS S4Sjr0SS S4Sjrg))dmatrix dmatrices incr_dbuilderincr_dbuildersN) PatsyError) DesignMatrix DesignInfo)EvalEnvironment) ModelDesc)design_matrix_buildersbuild_design_matrices) have_pandasasarray_or_pandasatleast_2d_column_defaultc[U[5(a[//XU5SU4$[U[5(aA[ U5S:Xa2[US[5(a[US[5(aU$[ US5(a6UR U5n[U[5(d[SU<S35e[U[5(a[R"U5n[U[5(a;[U[5(de[URUR/UUU5$g)Nr__patsy_get_model_desc__zbad value from z.__patsy_get_model_desc__) isinstancer r tuplelenhasattrrr rstr from_formular lhs_termlist rhs_termlist) formula_likedata_iter_makereval_env NA_actions bC:\Users\julio\OneDrive\Documentos\Trabajo\Ideas Frescas\venv\Lib\site-packages\patsy/highlevel.py_try_incr_buildersr"s, ++ "B4I Nq Q   <''   " |A 3 3 |A 3 3|788#<[T/5$)N)iter)datasr!r-_do_highlevel_design..data_iter_makersTF|r#)r return_typerz$don't know what to do with a length z matrices tupleT)subokc\>[R"X5n[(a<[U[R [R 45(a URnOSnTS:Xa:[USS9n[R "U5nURUl X l X4$[X5U4$)Nr2T)preserve_pandas) r from_arrayrrpandasSeries DataFrameindexrr,columns design_infor)mdefault_column_prefixdi orig_indexr8s r!_regularize_matrix0_do_highlevel_design.._regularize_matrixs&&q@B{z!fmmV=M=M-NOOWW ! k)-aF$$Q'OO " &$Q+Z88r#xr)dtypeyrBz#shape mismatch: outcome matrix has z rows, predictor matrix has z rowsz?index mismatch: outcome and predictor have incompatible indexes)rrr"r rrrrnpzerosshapefloatgetattrr equalsr@) rr6rr r8rr.lhsrhsrGrhs_orig_indexlhs_orig_indexs ` ` r!_do_highlevel_designrVsk!++ L  11)4 7  &xL$ $)  lE * *< A% (+L(9<&JS# 1,d K# 91c: ;((CIIaL!,E:C0c:'#}d;ZHHHH'#}d;ZHHHH 99Q<399Q< '25))A, ! N   %.*D!((88 X + %)n.DII %.*DII zr#r3c[R"USS9n[XX#U5upVURSS:wa [ S5eU$)a Construct a single design matrix given a formula_like and data. :arg formula_like: An object that can be used to construct a design matrix. See below. :arg data: A dict-like object that can be used to look up variables referenced in `formula_like`. :arg eval_env: Either a :class:`EvalEnvironment` which will be used to look up any variables referenced in `formula_like` that cannot be found in `data`, or else a depth represented as an integer which will be passed to :meth:`EvalEnvironment.capture`. ``eval_env=0`` means to use the context of the function calling :func:`dmatrix` for lookups. If calling this function from a library, you probably want ``eval_env=1``, which means that variables should be resolved in *your* caller's namespace. :arg NA_action: What to do with rows that contain missing values. You can ``"drop"`` them, ``"raise"`` an error, or for customization, pass an :class:`NAAction` object. See :class:`NAAction` for details on what values count as 'missing' (and how to alter this). :arg return_type: Either ``"matrix"`` or ``"dataframe"``. See below. The `formula_like` can take a variety of forms. You can use any of the following: * (The most common option) A formula string like ``"x1 + x2"`` (for :func:`dmatrix`) or ``"y ~ x1 + x2"`` (for :func:`dmatrices`). For details see :ref:`formulas`. * A :class:`ModelDesc`, which is a Python object representation of a formula. See :ref:`formulas` and :ref:`expert-model-specification` for details. * A :class:`DesignInfo`. * An object that has a method called :meth:`__patsy_get_model_desc__`. For details see :ref:`expert-model-specification`. * A numpy array_like (for :func:`dmatrix`) or a tuple (array_like, array_like) (for :func:`dmatrices`). These will have metadata added, representation normalized, and then be returned directly. In this case `data` and `eval_env` are ignored. There is special handling for two cases: * :class:`DesignMatrix` objects will have their :class:`DesignInfo` preserved. This allows you to set up custom column names and term information even if you aren't using the rest of the patsy machinery. * :class:`pandas.DataFrame` or :class:`pandas.Series` objects will have their (row) indexes checked. If two are passed in, their indexes must be aligned. If ``return_type="dataframe"``, then their indexes will be preserved on the output. Regardless of the input, the return type is always either: * A :class:`DesignMatrix`, if ``return_type="matrix"`` (the default) * A :class:`pandas.DataFrame`, if ``return_type="dataframe"``. The actual contents of the design matrix is identical in both cases, and in both cases a :class:`DesignInfo` object will be available in a ``.design_info`` attribute on the return value. However, for ``return_type="dataframe"``, any pandas indexes on the input (either in `data` or directly passed through `formula_like`) will be preserved, which may be useful for e.g. time-series models. .. versionadded:: 0.2.0 The ``NA_action`` argument. rr&rr)r r+rVrNrrr6rr r8rRrSs r!rrsS~&&x1=H%HJS yy|q T   Jr#c[R"USS9n[XX#U5upVURSS:Xa [ S5eXV4$)a?Construct two design matrices given a formula_like and data. This function is identical to :func:`dmatrix`, except that it requires (and returns) two matrices instead of one. By convention, the first matrix is the "outcome" or "y" data, and the second is the "predictor" or "x" data. See :func:`dmatrix` for details. rr&rr0rXrYs r!rr2sO&&x1=H%HJS yy|qFGG :r#)rr$)__all__numpyrLpatsyrpatsy.design_inforr patsy.evalr patsy.descr patsy.buildr r patsy.utilrrrr=r"rrrVrrr#r!rdsh F6& EPP F.bFOd "AXGVAXr#