Skip to content
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

polytopes_db_4d converted to new style package #26029

Closed
embray opened this issue Aug 9, 2018 · 25 comments
Closed

polytopes_db_4d converted to new style package #26029

embray opened this issue Aug 9, 2018 · 25 comments

Comments

@embray
Copy link
Contributor

embray commented Aug 9, 2018

This spkg is mentioned in #14467 and was apparently "huge" (and hence optional). But it is no longer listed under build/pkgs nor does it appear to be available on the download mirrors.


Here is a branch to convert it to a new style experimental (but, maybe optional?) package.

the tarball is the old *.spkg file, but as it's a tar file, it works

tarball url (see in checksum.ini), but it's the same as one gets
via ./sage -p polytopes_db_4d (which still works with old style pkfs)

A few options:

  1. If someone has a copy of this package we can convert it to a new-style SPKG (we will probably need to upload the tarball somewhere with enough space to host it).

Done.

CC: @mkoeppe @vbraun

Component: packages: huge

Author: Dima Pasechnik

Branch/Commit: b49f89a

Reviewer: Travis Scrimshaw

Issue created by migration from https://trac.sagemath.org/ticket/26029

@embray embray added this to the sage-8.4 milestone Aug 9, 2018
@slel
Copy link
Member

slel commented Aug 9, 2018

comment:1

Related discussions:

@slel
Copy link
Member

slel commented Aug 10, 2018

comment:2

The package is listed at:

@slel
Copy link
Member

slel commented Aug 10, 2018

comment:3

And it's available from each of the SageMath download mirrors. E.g.

etc.

The problems encountered with this huge package might instead have to do with

@embray
Copy link
Contributor Author

embray commented Aug 14, 2018

comment:4

As I wrote on sage-devel, we could keep supporting this package if it were repackaged as a .tar.<whatever compression method works best>, and we added an appropriate build/pkgs/polytopes_db_4d for it. We would then want to move it to a standard location on the mirrors, not under "spkg/huge". That, or leave it under "spkg/huge" (if there is some advantage to that--can mirrors opt not to carry "huge" packages?) but modify sage-download-file to be able to find tarballs under that path on the mirrors.

@embray embray modified the milestones: sage-8.4, sage-8.5 Oct 28, 2018
@slel
Copy link
Member

slel commented Nov 4, 2018

comment:6

The following shows sage can find packages in "huge":

$ sage --info polytopes_db_4d
Attempting to get on-line info for package polytopes_db_4d
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
>>> Found polytopes_db_4d-1.0
...

The package cannot be installed with sage -i because it is an "old-style SPKG"

$ sage -i polytopes_db_4d
...
Error: package 'polytopes_db_4d' not found
Note: if it is an old-style package, use -p instead of -i to install it

but sage -p can install "old-style spkg" packages that still work, including this one.

$ sage -p polytopes_db_4d
Attempting to download package polytopes_db_4d
>>> Checking online list of optional packages.
>>> Checking online list of experimental packages.
>>> Checking online list of huge packages.
>>> Found polytopes_db_4d-1.0
================================== NOTE ==================================
You are about to download and install an old-style package. While this
might still work fine, old-style packages are unmaintained and deprecated.

This package will be removed in future versions of SageMath. If you care
about this package, you should make a proper new-style package instead.
For more information about making Sage packages, see
http://doc.sagemath.org/html/en/developer/packaging.html
==========================================================================
Are you sure (automatically continuing in 30 seconds) [Y/n]?

Once this is done and after restarting Sage, one can follow the
SageMath documentation on using the palp_database of reflexive Hodge 4-polytopes.
I tried it in Sage 8.4 as installed on the "k8s" CoCalc server for development,
which currently runs Ubuntu 17.04.

sage: version()
'SageMath version 8.4, Release Date: 2018-10-17'
sage: from sage.geometry.polyhedron.palp_database import Reflexive4dHodge
sage: ref = Reflexive4dHodge(1, 101)
sage: next(iter(ref)).Vrepresentation()
(A vertex at (-1, -1, -1, -1),
 A vertex at (0, 0, 0, 1),
 A vertex at (0, 0, 1, 0),
 A vertex at (0, 1, 0, 0),
 A vertex at (1, 0, 0, 0))

@embray
Copy link
Contributor Author

embray commented Dec 28, 2018

comment:7

Retargeting some of my tickets (somewhat optimistically for now).

@embray embray modified the milestones: sage-8.5, sage-8.7 Dec 28, 2018
@embray
Copy link
Contributor Author

embray commented Mar 25, 2019

comment:8

Removing most of the rest of my open tickets out of the 8.7 milestone, which should be closed.

@embray embray removed this from the sage-8.7 milestone Mar 25, 2019
@embray embray added the pending label Mar 25, 2019
@embray
Copy link
Contributor Author

embray commented Apr 19, 2019

comment:9

According to Andrey Novoseltev:

Data originates from http://hep.itp.tuwien.ac.at/~kreuzer/CY/

The whole list can be generated using PALP (a standard package in Sage), but when they have done it first, it took about a year on multiple computers, so there is sense in just downloading these polytopes. Sage package contains precomputed data for Hodge numbers as well, allowing quick search for particular cases. Volker knows more about exact details, I was just happily using the result.

While we are at it: it would be awesome if installation of this package after upgrade was faster. "Installation" just means unpacking files and copying them somewhere, but it takes something like 45 minutes. Some time ago I asked to use parallel decompressor if it is available in the system, which helped a lot, but then it stopped again.

As I wrote on sage-devel, perhaps it would make sense to host this data (as well as the 3D polytopes; why not?) on an online database somewhere that can be easily queried (including by the code in Sage which uses this data)? This way it is possible to use as-needed without downloading the entire, very large database (though perhaps with the possibility of pre-downloading/caching all or parts of it as needed).

It would be very easy to write a simple web service, and perhaps the data and service could be hosted on sagemath.org. This might also be a good opportunity for some MitM synergy. There is a workshop later this year on mathematical data, and frameworks and services for accessing them, so that might be a good opportunity to work on such a project (I would be happy to help, especially if someone can help me with the math end of things as I have no idea what a reflexive Hodge polytope is much less how it would be represented in a MitM framework): https://opendreamkit.org/2019/08/17/WorkshopOnDataInMathematics/

@dimpase
Copy link
Member

dimpase commented Apr 23, 2019

comment:10

A reflexive polytope is a full-dimensional lattice polytope (i.e. the vertices have integer coordinates), containing the origin in the interior, so that its dual
is also a lattice polytope. All this is readily available in Sage.

@novoselt
Copy link
Member

comment:11

3D polytopes take so little space, that there is no sense at all removing them from Sage in their current form. As for 4D, there are probably very few people who are using them and so there is a lack of effort to do something about them. On the other hand, since there are papers referring to the use of this package in Sage, it would be nice to support repeating those computations in some way, even if installation is "non-standard".

@dimpase
Copy link
Member

dimpase commented Jun 9, 2020

Author: Dima Pasechnik

@dimpase
Copy link
Member

dimpase commented Jun 9, 2020

Commit: 2ed5a53

@dimpase
Copy link
Member

dimpase commented Jun 9, 2020

New commits:

2ed5a53converting polytopes_db_4d into a new style package

@dimpase

This comment has been minimized.

@dimpase
Copy link
Member

dimpase commented Jun 9, 2020

Branch: u/dimpase/packages/refpoly4d

@dimpase dimpase added this to the sage-9.2 milestone Jun 9, 2020
@dimpase dimpase removed the pending label Jun 9, 2020
@dimpase dimpase changed the title Missing spkg: polytopes_db_4d polytopes_db_4d converted to new style package Jun 9, 2020
@tscrim
Copy link
Collaborator

tscrim commented Jun 10, 2020

comment:13

Do we want this to be experimental or optional? I feel like optional would be the better option for this.

@mkoeppe
Copy link
Contributor

mkoeppe commented Jun 10, 2020

comment:14

I also think it should be "optional"

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 11, 2020

Branch pushed to git repo; I updated commit sha1. New commits:

b49f89amake it optional

@sagetrac-git
Copy link
Mannequin

sagetrac-git mannequin commented Jun 11, 2020

Changed commit from 2ed5a53 to b49f89a

@dimpase
Copy link
Member

dimpase commented Jun 11, 2020

comment:16

OK, done

@tscrim
Copy link
Collaborator

tscrim commented Jun 13, 2020

comment:17

Thanks. I am ready to set a positive review. Any objections?

@tscrim
Copy link
Collaborator

tscrim commented Jun 13, 2020

Reviewer: Travis Scrimshaw

@mkoeppe
Copy link
Contributor

mkoeppe commented Jun 13, 2020

comment:18

No objection; I haven't tried it though because downloading was taking too long.

@tscrim
Copy link
Collaborator

tscrim commented Jun 14, 2020

comment:19

It built for me without any problems, so I am setting it to positive.

@vbraun
Copy link
Member

vbraun commented Jun 22, 2020

Changed branch from u/dimpase/packages/refpoly4d to b49f89a

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants