You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
15$\begingroup$ My computer screen smells the same with this displayed as it usually does. $\endgroup$Will Jagy– Will Jagy2010-09-10 19:24:50 +00:00Commented Sep 10, 2010 at 19:24
-
4$\begingroup$ That is indeed reassuring. $\endgroup$Cam McLeman– Cam McLeman2010-09-10 19:25:48 +00:00Commented Sep 10, 2010 at 19:25
-
$\begingroup$ Cam, a possibly easier question is whether the Baker-Heegner-Stark answer had to be less than or equal to the Schoof answer, once the former was known to be finite. $\endgroup$Will Jagy– Will Jagy2010-09-10 19:58:30 +00:00Commented Sep 10, 2010 at 19:58
-
2$\begingroup$ No, I take it back. Stark has a very accurate test for conjectures based on the first result being the most difficult proof in that area of mathematics. As the number 163 was surely known for both problems, an easy answer to my problem, or your original, gives an easy proof of Baker-Heegner-Stark, therefore there is no such easy relationship. The relationship is a coincidence. Quod Erat Demonstarkum. $\endgroup$Will Jagy– Will Jagy2010-09-10 20:10:54 +00:00Commented Sep 10, 2010 at 20:10
-
$\begingroup$ See if I can get Stark's test correct. Use apostrophe for negation, S for Baker-Heegner-Stark, C for some conjecture. If we have the implication S' --> C, then Stark believes C pending further investigation. Why, you ask? Worry not, I shall tell you. The contrapositive is C' --> S. If C actually turned out to be false, this would provide an easy proof of S $\endgroup$Will Jagy– Will Jagy2010-09-10 20:32:47 +00:00Commented Sep 10, 2010 at 20:32
|
Show 8 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. ag.algebraic-geometry), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you