I'm currently working on a Random Data Compression effort myself.  I know 
many of you have heard it all before and will claim it can't be done.  I 
don't intend to debate this here as I don't check this group enough.  But 
your more than welcome to follow my thread discussion that I will be 
updating often concerning this.  You can find the thread here and I welcome 
your discussion there.

http://www.tretbase.com/forum/viewtopic.php?f=13&t=76#p167

Paul 

"Paul" <paul@tretbase.com> wrote in message 
news:BkDQl.77596$5N7.2039@newsfe09.iad...
> I'm currently working on a Random Data Compression effort myself. I know 
> many of you have heard it all before and will claim it can't be done.

We know it can't be done.

> I don't intend to debate this here as I don't check this group enough. 
> But your more than welcome to follow my thread discussion that I will be 
> updating often concerning this.  You can find the thread here and I 
> welcome your discussion there.
>
> http://www.tretbase.com/forum/viewtopic.php?f=13&t=76#p167

I must be a masochist; I went to your forum.
There were four messages, all (I assume) from you.
All were from over a year ago.
You said you were going to update the thread at least weekly.
What happened?

You also stated your current concept was to take every 16 bits of data,
and compress it to 15 bits. How will this work? 16 bits have 64K
combinations. 15 bits have 32K combinations. On avarage there will
be two strings of 16 bits compress to each string of 15 bits.
How does your decompressor know which 16 bit string is represented
by any given 15 bit string?

Pete 

On 19 Mai, 20:59, "Paul" <p...@tretbase.com> wrote:
> I'm currently working on a Random Data Compression effort myself.

What's your model of this "random data"? Is it uniform distribution
across all possible binary files of the same size?

  [ L(a) = L(b)  implies  P(a) = P(b) ]
  [ P: a file's probability, L: a file's length ]

This is a simple yes/no question.

In case you don't know what I'm talking about I encourage you to take
the time to look up the terms you don't understand. You might even get
an epiphany if you do.


Cheers!
SG

"Pete Fraser" <pfraser@covad.net> wrote in message 
news:nNOdneLxHtYMmo7XnZ2dnUVZ_ridnZ2d@supernews.com...
> "Paul" <paul@tretbase.com> wrote in message 
> news:BkDQl.77596$5N7.2039@newsfe09.iad...
>> I'm currently working on a Random Data Compression effort myself. I know 
>> many of you have heard it all before and will claim it can't be done.
>
> We know it can't be done.
>
>> I don't intend to debate this here as I don't check this group enough. 
>> But your more than welcome to follow my thread discussion that I will be 
>> updating often concerning this.  You can find the thread here and I 
>> welcome your discussion there.
>>
>> http://www.tretbase.com/forum/viewtopic.php?f=13&t=76#p167
>
> I must be a masochist; I went to your forum.
> There were four messages, all (I assume) from you.
> All were from over a year ago.
> You said you were going to update the thread at least weekly.
> What happened?
>
> You also stated your current concept was to take every 16 bits of data,
> and compress it to 15 bits. How will this work? 16 bits have 64K
> combinations. 15 bits have 32K combinations. On avarage there will
> be two strings of 16 bits compress to each string of 15 bits.
> How does your decompressor know which 16 bit string is represented
> by any given 15 bit string?
>
> Pete
>

You must have been looking in the wrong area Pete, the compression messages 
are under General Discussion and very recent (within the last week).

Paul 

Paul:
> You must have been looking in the wrong area Pete, the compression 
> messages are under General Discussion and very recent (within the last 
> week).

No. I was just being dumb and reading your "joined" date
rather than the posting date.

What is your response to my 16-bit to 15-bit question below?

Pete:
>> You also stated your current concept was to take every 16 bits of data,
>> and compress it to 15 bits. How will this work? 16 bits have 64K
>> combinations. 15 bits have 32K combinations. On avarage there will
>> be two strings of 16 bits compress to each string of 15 bits.
>> How does your decompressor know which 16 bit string is represented
>> by any given 15 bit string?

"Pete Fraser" <pfraser@covad.net> wrote in message 
news:PPydnRnIkeCslYnXnZ2dnUVZ_j2dnZ2d@supernews.com...
> Paul:
>> You must have been looking in the wrong area Pete, the compression 
>> messages are under General Discussion and very recent (within the last 
>> week).
>
> No. I was just being dumb and reading your "joined" date
> rather than the posting date.
>
> What is your response to my 16-bit to 15-bit question below?
>
> Pete:
>>> You also stated your current concept was to take every 16 bits of data,
>>> and compress it to 15 bits. How will this work? 16 bits have 64K
>>> combinations. 15 bits have 32K combinations. On avarage there will
>>> be two strings of 16 bits compress to each string of 15 bits.
>>> How does your decompressor know which 16 bit string is represented
>>> by any given 15 bit string?
>
>
>


Hi Pete, I can't go into "How" it will work just yet - at least not in any
detail until I have protected the idea and first I need to prove the concept
to myself even more.  So far so good on that front but I have a bit more to
do.  I need to some calculations and currently I'm "missing" some output
data that I can generate ok on smaller numbers by hand.  So I need to debug
and build a better generator to prove my concept (that is what I need to
work on which is very complex).   If I were to give you an answer to your
question regarding the 16 bits to 15  bits, I would be giving away to much.
Be sure to check the thread I posted weekly if you want to follow along.

Paul 

>Paul" <paul@tretbase.com> wrote in message
>news:BkDQl.77596$5N7.2039@newsfe09.iad...
> I'm currently working on a Random Data Compression effort myself.  I know
> many of you have heard it all before and will claim it can't be done.  I
> don't intend to debate this here as I don't check this group enough.  But
> your more than welcome to follow my thread discussion that I will be
> updating often concerning this.  You can find the thread here and I
> welcome your discussion there.
>
> http://www.tretbase.com/forum/viewtopic.php?f=13&t=76#p167
>
> Paul

New  update
http://www.tretbase.com/forum/viewtopic.php?f=13&t=76&start=10#p179