I = matchingFieldIdeal L
A matching field $\Lambda$ for the Grassmannian Gr$(k,n)$ associates to each subset $J = \{j_1 < \dots < j_k\}$ an ordering of that subset $\Lambda(J) = (j_{\sigma(1)}, \dots, j_{\sigma(k)})$ for some permutation $\sigma \in S_k$. The monomial map associated to a matching field $\Lambda$ is defined as the map that sends each Pluecker coordinate $p_J$ to the monomial sgn$(\sigma)x_{1, \Lambda(J)_1} x_{2, \Lambda(J)_2} \cdots x_{k, \Lambda(J)_k}$ where sgn$(\sigma) \in \{+1, -1\}$ is the sign of the permutation. The matching field ideal is the kernel of this monomial map.
|
|
|
|
The analogous setup holds for flag matching fields. A flag matching field can be thought of as a union of Grassmannian matching fields. The inclusion of the Grassmannian matching field naturally extends to an inclusion of the corresponding ideals. The flag matching field ideals are also generated by 'incident relations' that involve Pluecker coordinates from distinct pairs of Grassmannians within the flag variety.
|
|
The functions matchingFieldIdeal and plueckerIdeal both construct ideals that belong to the same polynomial ring. Similarly, the ring maps constructed by the function plueckerMap and matchingFieldRingMap have the same target ring.
|
|
|
|
|
|
If the matching field is not coherent, then the matching field ideal can be constructed by setting the option MonomialOrder to "none". Doing this sets the monomial order of the target polynomial ring above to GRevLex.
|
|
|
|
The option Strategy determines how the matching field ideal is computed. The default uses the package FourTiTwo. This strategy works by passing in the matrix of the toric ideal to toricGroebner with the correct weight vector. In the case of Grassmannian matching fields, the columns of the matrix of the toric ideal are exactly the vertices of the matching field polytope. For a flag matching field $\Lambda$, the matrix of the toric ideal is the top-justified juxtaposition of such matrices for the Grassmannian matching fields contained in $\Lambda$. On the other hand, the strategy "M2" simply uses the in-built function to compute the kernel of the map matchingFieldRingMap.
For some versions of the package FourTiTwo, the strategy "4ti2" may not correctly take into account the weights. See the caveat in the documentation of the function toricGroebner. If there are any problems, it may be more reliable to use the option "M2".
The object matchingFieldIdeal is a method function with options.