100 byte file now compresses to 1 byte instead of 7 bytes. my program takes
89 seconds to do this but i can make this faster with assembly.
i need to talk to a lawyer to get patents. i heard ibm has patent on all
compression, how to get them to pay me?
If I send you 256 compressed files, can you send me back the 100 bytes
originals ?
G.
If you find the *magic* number, the method to take down all mathematics as
we know it, why not make it public?
Wouldnt you rather see what the people can evolve to with the new
information?
At least for me there isnt enough money in the world to compare to that...
but thats me..
Regards
Fredrik
"Tim Bernard" <notmy...@server.com> wrote in message
news:NI4qa.75614$Si4....@rwcrnsc51.ops.asp.att.net...
"Giovanni Motta" <g...@ieee.org> wrote in message
news:3EA8DB95...@ieee.org...
why can do a very simple test to see if your compressor really works:
1 - we send you some 100byte files to compress (around 300 files)
2 - you send us back the files compressed
3 - we send you one or two of the compressed files
4 - you send us back the original files for those (3)
to compress 300 x 100bytes files at 90s will take you 450 min
(6h30m), not so long.
well, attached is a file with 300 different 100 byte lines.
Bye,
- Salva
Tim Bernard wrote:
> My compression works with 8 bit ascii post your files here. for quicker
> response post some 7 byte compressed it will take a little longer for me to
> run with 1 byte files
I am not in a rush, I'll wait for the time consuming response. Getting
the answer is also important to you since you can speed up your
decompressor with that (see hint).
I would like to see the uncompressed result of the 256 files containing
1 byte only with the byte going from 0x00 to 0xFF.
If there is any byte that doesn't compress correctly just mark the
corresponding byte "Illegal".
I can use a table like:
Content Decompressed
00 0234123134.... 100 bytes in hex notation here.... F54D
01 Illegal
02 FD0ABC1233.... 100 bytes in hex notation here.... F000
.. ..
.. ..
FF DFAB010234.... 100 bytes in hex notation here.... D0AB
Giovanni
P.S. Hint to speed up your decompressor: Build the table once for all
and use table lookup to decompress. It rarely gets faster than that.
I can make it lots and lots faster for you easily.
First, the decompressor: Simply make a lookup table, indexed by the 1
compressed byte. This only takes 256*100 bytes of space and will be
blindingly fast.
Then, the compressor: Search through the lookup table until you find your
100-byte file and return the index. As you only have to search through
25600 bytes, this will also be quite fast, in the order of milliseconds.
SaSW, Willem (at stack dot nl)
--
Disclaimer: I am in no way responsible for any of the statements
made in the above text. For all I know I might be
drugged or something..
No I'm not paranoid. You all think I'm paranoid, don't you !
#EOT
> why can do a very simple test to see if your compressor really works:
>
> 1 - we send you some 100byte files to compress (around 300 files)
>
> 2 - you send us back the files compressed
oops, I forgot to say that obviously you have to use the 100 to 1
compressor!
Bye,
- Salva
STOP FEEDING THE IDIOT TROLL!
> ) Ok ive been working on this for the last 3 days straight and have improved
> ) compression.
> )
> ) 100 byte file now compresses to 1 byte instead of 7 bytes. my program takes
> ) 89 seconds to do this but i can make this faster with assembly.
>
> I can make it lots and lots faster for you easily.
>
> First, the decompressor: Simply make a lookup table, indexed by the 1
> compressed byte. This only takes 256*100 bytes of space and will be
> blindingly fast.
>
> Then, the compressor: Search through the lookup table until you find your
> 100-byte file and return the index. As you only have to search through
> 25600 bytes, this will also be quite fast, in the order of milliseconds.
But, but... But then it is easy for a child to see that it doesn't
work for all inputs. This will utterly shatter his perception of the
undoable...
But surely if you run the compresser on it again you could make it 1 bit.
That would be much better.
Tim, I have a stream which is one byte (8 bits) in size. The value of that
byte is zero.
That is, 8 bits all set to zero.
What was the original 100 byte stream?
-Michael A Maniscalco
"Tim Bernard" <notmy...@server.com> wrote in message
news:NI4qa.75614$Si4....@rwcrnsc51.ops.asp.att.net...
> Ok ive been working on this for the last 3 days straight and have improved
> compression.
>
> 100 byte file now compresses to 1 byte instead of 7 bytes. my program takes
> 89 seconds to do this but i can make this faster with assembly.
I'm sure if you tried a bit harder you could get 100 bytes to compress
to 0 bytes. THAT would be ultimate compression.
Gib
Bah; I do that regularly. Only problem is, it's lossy. I think the
program to do this is called 'rm'...
Here is the decompression of your sample file this should prove all
naysayers wrong and encourage discussion on potential uses of my program
"True! nervous, very, very dreadfully nervous I had been and am; but why
will you say that I am mad? "
And it's possible to get back the original, without any loss!
Just copy it to a floppy or a CD first! ;-)
Well, seriously, I think it's the *definition* of compression which is
the problem here. I've not read anywhere that he can recreate the original.
/Mikael
He said he could do it losslessly, which by definition is supposed to mean
he can recreate the original.
--
Dale King