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

Determine planned extent of classical modular forms #873

Closed
davidfarmer opened this issue Mar 28, 2016 · 10 comments
Closed

Determine planned extent of classical modular forms #873

davidfarmer opened this issue Mar 28, 2016 · 10 comments
Labels
CMF Classical modular forms critical Serious problem that directly impacts www.lmfdb.org production issue Problem currently impacting www.lmfdb.org
Milestone

Comments

@davidfarmer
Copy link
Member

Change the ranges in issues #448, #450, and #451 to something reasonable, and make
a similar decision for very small weight and very small level. Then describe the available data in
a data extent knowl.

@davidfarmer davidfarmer added CMF Classical modular forms critical Serious problem that directly impacts www.lmfdb.org April labels Mar 28, 2016
@davidfarmer davidfarmer added this to the v1.0 milestone Mar 28, 2016
@davidfarmer davidfarmer removed April critical Serious problem that directly impacts www.lmfdb.org labels May 2, 2016
@davidfarmer
Copy link
Member Author

The "critical" label was removed because we now have a data extent knowl at the top of
/ModularForm/GL2/Q/holomorphic/

@AndrewVSutherland AndrewVSutherland added the critical Serious problem that directly impacts www.lmfdb.org label May 20, 2016
@AndrewVSutherland
Copy link
Member

The critical label has been added back because the data extent knowl (displayed on the top of http://www.lmfdb.org/ModularForm/GL2/Q/holomorphic/) does not agree with the data.

Once it does we can close this issue but until it does I think it is crtical.

I don't think we need to keep issues #448, #450, and #451 open; if someone wants to create a new issue labeled as a feature request with a desired range of classical modular forms, that's fine, but it probably makes sense to wait until this issue is addressed.

@davidfarmer
Copy link
Member Author

I am okay with closing #448, #450, and #451.

The data extent knowl explains what we have, and later someone may wish
to specifically propose another rectangle (such as a rectangle for
real characters).

On Thu, 19 May 2016, Andrew Sutherland wrote:

The critical label has been added back because the data extent knowl (displayed on the top of
http://www.lmfdb.org/ModularForm/GL2/Q/holomorphic/) does not agree with the data.

Once it does we can close this issue but until it does I think it is crtical.

I don't think we need to keep issues #448, #450, and #451 open; if someone wants to create a new
issue labeled as a feature request with a desired range of classical modular forms, that's fine, but
it probably makes sense to wai t until this issue is addressed.


You are receiving this because you authored the thread.
Reply to this email directly or view it on
GitHub[AAM6LCOQvQTaaq-jqpgipnudUxdciFLhks5qDRFtgaJpZM4H5-pr.gif]

@AndrewVSutherland
Copy link
Member

We have made some good forward progress. With #1376 closed, we now have complete data for all the spaces with trivial character in the ranges (k,N) in [2,40] x [1,24] and (k,N) in [2,12] x [1,100](in fact we also have %28k,N%29 in [2,40] x {25}, which is beyond the extent listed in the knowl -- I will update it). It remains to address the spaces with non-trivial character. I note that for N=41 both k=5 and k=7 are definitely missing, and the completeness (and correctness) of the remaining data still needs to be verified (this is #1248).

@sehlen
Copy link
Contributor

sehlen commented May 21, 2016

Actually, it is [2, 40] x [2, 25]. It's very easy to extend that but next
week we'll concentrate on fixing non-trivial character data.

On Sat, May 21, 2016, 06:31 Andrew Sutherland notifications@github.com
wrote:

We have made some good forward progress. With #1376
#1376 closed, we now have complete
data for all the spaces with trivial character in the ranges (k,N) in
[2,40] x [1,24] and (k,N) in [2,12] x 1,100. It remains to address the
spaces with non-trivial character. I note that for N=41 both k=5 and k=7
are definitely missing, and the completeness (and correctness) of the
remaining data still needs to be verified (this is #1248
#1248).


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#873 (comment)

@sehlen
Copy link
Contributor

sehlen commented May 21, 2016

I meant [2, 40] x [1, 25]. Will extend this soon.

On Sat, May 21, 2016, 08:37 Stephan Ehlen stephan@die-ehlens.de wrote:

Actually, it is [2, 40] x [2, 25]. It's very easy to extend that but next
week we'll concentrate on fixing non-trivial character data.

On Sat, May 21, 2016, 06:31 Andrew Sutherland notifications@github.com
wrote:

We have made some good forward progress. With #1376
#1376 closed, we now have
complete data for all the spaces with trivial character in the ranges (k,N)
in [2,40] x [1,24] and (k,N) in [2,12] x 1,100. It remains to address
the spaces with non-trivial character. I note that for N=41 both k=5 and
k=7 are definitely missing, and the completeness (and correctness) of the
remaining data still needs to be verified (this is #1248
#1248).


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#873 (comment)

@AndrewVSutherland
Copy link
Member

AndrewVSutherland commented May 21, 2016

@sehlen, right I actually updated the extent knowl earlier to reflect the expanded range. But I agree that we should focus on completing/fixing the non-trivial character data before extending it further.

@AndrewVSutherland
Copy link
Member

I extended the range of pages tested by emf_test_pages.py to include (k,N) = [2,12] x [1,100] and found a problem with k=12 and N=83, see #1248 (comment).

@AndrewVSutherland AndrewVSutherland added the production issue Problem currently impacting www.lmfdb.org label Jun 8, 2016
@davidfarmer davidfarmer modified the milestones: v1.1, v1.0 Jun 8, 2016
@AndrewVSutherland
Copy link
Member

There are still many holes, even for trivial character, e.g. http://www.lmfdb.xyz/ModularForm/GL2/Q/holomorphic/17/6/1/.

Several of these show up in the flasklog on the cloud server, and the pattern suggests that it is people (not robots) clicking on them.

@AndrewVSutherland
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CMF Classical modular forms critical Serious problem that directly impacts www.lmfdb.org production issue Problem currently impacting www.lmfdb.org
Projects
None yet
Development

No branches or pull requests

3 participants