Sets of integers that do not contain long arithmetic progressions.

O'Bryant, Kevin

The Electronic Journal of Combinatorics [electronic only] (2011)

  • Volume: 18, Issue: 1, page Research Paper P59, 15 p., electronic only-Research Paper P59, 15 p., electronic only
  • ISSN: 1077-8926

How to cite

top

O'Bryant, Kevin. "Sets of integers that do not contain long arithmetic progressions.." The Electronic Journal of Combinatorics [electronic only] 18.1 (2011): Research Paper P59, 15 p., electronic only-Research Paper P59, 15 p., electronic only. <http://eudml.org/doc/228885>.

@article{OBryant2011,
author = {O'Bryant, Kevin},
journal = {The Electronic Journal of Combinatorics [electronic only]},
keywords = {arithmetic progressions},
language = {eng},
number = {1},
pages = {Research Paper P59, 15 p., electronic only-Research Paper P59, 15 p., electronic only},
publisher = {Prof. André Kündgen, Deptartment of Mathematics, California State University San Marcos, San Marcos},
title = {Sets of integers that do not contain long arithmetic progressions.},
url = {http://eudml.org/doc/228885},
volume = {18},
year = {2011},
}

TY - JOUR
AU - O'Bryant, Kevin
TI - Sets of integers that do not contain long arithmetic progressions.
JO - The Electronic Journal of Combinatorics [electronic only]
PY - 2011
PB - Prof. André Kündgen, Deptartment of Mathematics, California State University San Marcos, San Marcos
VL - 18
IS - 1
SP - Research Paper P59, 15 p., electronic only
EP - Research Paper P59, 15 p., electronic only
LA - eng
KW - arithmetic progressions
UR - http://eudml.org/doc/228885
ER -

NotesEmbed ?

top

You must be logged in to post comments.

To embed these notes on your page include the following JavaScript code on your page where you want the notes to appear.

Only the controls for the widget will be shown in your chosen language. Notes will be shown in their authored language.

Tells the widget how many notes to show per page. You can cycle through additional notes using the next and previous controls.

    
                

Note: Best practice suggests putting the JavaScript code just before the closing </body> tag.