[seqfan] Re: A001476

David Wilson davidwwilson at comcast.net
Sat Feb 25 21:07:54 CET 2012

I take it you are arguing that if "full" includes b-files, the meaning 
of "fini" and "full" becomes more or less redundant, since almost all 
"fini" sequences are "full" as well in the b-file sense.

Perhaps this is true, but I doubt it is universally so. It is not overly 
difficult to specify very long finite sequences for which a full b-file 
would not be practical. For example "Numbers not the sum of distinct 4th 

My argument is that "full" meaning "all elements are in the OEIS (in the 
STU lines or b-file)" is arguably more useful than "all element are in 
the STU lines". At the very least, if "full" included b-files, then it 
would be easy to identify candidates for b-file work: "fini" but not "full".

On 2/25/2012 3:37 PM, Alonso Del Arte wrote:
> Where would the line be drawn? Is there a finite sequence in the OEIS that
> is nevertheless too long to be given in full in the B-file?
> When I wrote the first draft of
> http://oeis.org/wiki/Clear-cut_examples_of_keywords I looked long and hard
> for a finite sequence with a long B-file. A056757 was the best I could
> find, with a little over fifty thousand terms total. A finite sequence with
> two or three hundred terms wouldn't have been a clear-cut example of
> keyword:fini -keyword:full.
> Al
> On Sat, Feb 25, 2012 at 12:22 PM, David Wilson<davidwwilson at comcast.net>wrote:
>> A001476 is an example of a finite sequence that is not complete in the STU
>> lines, but is complete in the b-file.
>> Perhaps we should mark such sequences as "full" since the data is
>> available.
>> ______________________________**_________________
>> Seqfan Mailing list - http://list.seqfan.eu/

More information about the SeqFan mailing list