-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
matrix(QQ,foo)
not working for vertices_and_rays
output
#3524
Comments
matrix(QQ,foo)
not workingmatrix(QQ,foo)
not working for vertices_and_rays
output
Thanks for fixing the issue title, @lgoettgens! I've changed the labels, since this is more an issue in polyhedral geometry:
|
The issue with directly converting this to an Oscar matrix is somewhat related to what you complained about in the other issue, i.e. vectors losing type information. Merging the rays and vertices into one matrix might produce something like
In general I would really recommend not using This issue is basically the same as #2313 |
@benlorenz Got it. When using
|
You can use these instead:
|
Oh wow, I didn't know these existed, thanks! Is there by any chance also a constructor for |
There is this one function polyhedral_complex(f::scalar_type_or_field,
v::AbstractCollection[PointVector],
vi::IncidenceMatrix,
r::AbstractCollection[RayVector],
ri::IncidenceMatrix,
L::Union{AbstractCollection[RayVector], Nothing} = nothing;
non_redundant::Bool = false) but it doesn't seem to work correctly with the SubobjectIterators right now, we will check it and add it to the docs. Using matrices does work though: julia> ppc = polyhedral_complex(QQ,
matrix(QQ,vertices(PC)),
vertex_indices(maximal_polyhedra(PC)),
matrix(QQ,rays(PC)),
ray_indices(maximal_polyhedra(PC)))
Polyhedral complex in ambient dimension 2 |
@benlorenz wrote:
Agreed, so "someone"(TM) should work on this |
@YueRen if this is important for you, please yell (or even better, fix it yourself ;-) but more seriously: just complain so we can prioritize it and assign someone to do it) |
Apologies for the very crude report (busy with workshop), but the following errors were encountered with @yassineELMAAZOUZ
The text was updated successfully, but these errors were encountered: