Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.compression > #2062 > unrolled thread

New Data storage method with severe compression capabilities.

Back to article view | Back to comp.compression

Contents

  New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-04 16:02 -0800
    Re: New Data storage method with severe compression capabilities. Noob <root@127.0.0.1> - 2013-11-05 10:03 +0100
      Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-05 04:44 -0800
    Re: New Data storage method with severe compression capabilities. Sebastian Garth <sebastiangarth@gmail.com> - 2013-11-07 23:28 -0800
      Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 01:00 -0800
    Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 04:56 -0800
    Re: New Data storage method with severe compression capabilities. Sebastian Garth <sebastiangarth@gmail.com> - 2013-11-08 09:50 -0800
      Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 10:41 -0800
        Re: New Data storage method with severe compression capabilities. Sebastian Garth <sebastiangarth@gmail.com> - 2013-11-08 10:57 -0800
          Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 13:25 -0800
            Re: New Data storage method with severe compression capabilities. pfraser <pete_fraser@comcast.net> - 2013-11-08 18:05 -0800
              Re: New Data storage method with severe compression capabilities. Sebastian Garth <sebastiangarth@gmail.com> - 2013-11-08 18:59 -0800
                Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 19:06 -0800
        Re: New Data storage method with severe compression capabilities. Thomas Richter <thor@math.tu-berlin.de> - 2013-11-08 22:28 +0100
          Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-08 16:40 -0800
            Re: New Data storage method with severe compression capabilities. Thomas Richter <thor@math.tu-berlin.de> - 2013-11-09 17:31 +0100
              Re: New Data storage method with severe compression capabilities. glen herrmannsfeldt <gah@ugcs.caltech.edu> - 2013-11-09 19:02 +0000
    Re: New Data storage method with severe compression capabilities. Fibonacci Code <anglikai@gmail.com> - 2013-11-11 05:48 -0800
    Re: New Data storage method with severe compression capabilities. Fibonacci Code <anglikai@gmail.com> - 2013-11-11 06:03 -0800
      Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-11 06:13 -0800
        Re: New Data storage method with severe compression capabilities. Fibonacci Code <anglikai@gmail.com> - 2013-11-12 06:57 -0800
          Re: New Data storage method with severe compression capabilities. Michael Harrington <michaelharrington4rep@gmail.com> - 2013-11-12 09:40 -0800

Page 1 of 2  [1] 2  Next page →

#2062 — New Data storage method with severe compression capabilities.

I am announcing my creation, a 3 part invention pertaining to a Solid Physical Drive. Physical as in it is made up of small parts, not electronic in manner, but in shapes, colors, and the absence of physical parts (Called Scaling, see below)

After much research I have concluded that a Physical Drive using Colors, Shapes, and a 2 function aspect I call Scaling will greatly increase how much data can be stored in a given inch². It not only represents a means of storage in a smaller space but has strong encryption qualities. Finally it represents a means to replace existing Long-Term storage with a far more stable format. 



The theories behind what I do shall be obvious to experts, when they see it. But let me try to describe it for laymen. I take a set of data and make a 3d (or 1d excepting less storage) representation of it. Via Scaling I can change the X axis, the Y axis, or the Z axis to certain extents to change the total possible outcomes. I can also exclude some portions entirely, leaving “Empty spots”.

Adding Colors, which by the way the Human Eye can see 10,000,000 of, we can vastly increase our pool. Colors are very small in size, smaller than the “Pits” in current magnetic based hard-drives. Memory currently takes up a space of about 2.4 microns by 2.1 microns. The visible light spectrum is approximately 400 to 700 nanometers in size. This is .4 to .7 Microns. Light currently affords a far greater potential memory density than standard magnetic memory. However 3D printing is not quite to that point, but we can easily squeeze in about an extra 10% in storage with just light alone at our current tech. 

However this Scaling method is not done. Scaling in my invention also allows “empty spots” as defined above. A standard Pascals Triangle will be useful for math here. You can take a given line of binary, and then do the following: 

First is the whole of the normal values, if 10 bits, then we have 1024 outcomes. Then we move to 9 bits and take one from the 10 bits. This is 9 bits with 10 possible variations. This is (2^9)*10. Next we move to 8 bits with 45 possible variations. This is (2^8)*45. Next 7 bits with 120 variations (2^7)*120 and then we go on for (2^6)*210, (2^5)*252, (2^4)*210, (2^3)*120, (2^2)*45 and (2^1)*10. We get 58,024 total outcomes or 15.824 (rounded) bits. 

We can also just see the empty spots as spacers. Spacing out a sequence of 1mb would mean seeing it increase in size, but the addition of spacers would mean more potential outcomes. This would mean we would have a much larger effective memory size. 

More so, we can turn 3D structures into 2D structures by just partitioning the layers separately. This means we can utilize shapes, scaling, and color into standard binary without due issue. 

In a physical format we also find that shapes are detectable at very small sizes. For some technical reasons (We need to keep our detector reasonably small) we should keep this near the size of color. Shapes is a way to encode higher amounts of data as well as provide some unusually robust encryption capabilities. In fact the combined whole (Shapes, Colors, Scaling) makes encoded Gigabytes so astronomically huge in complexity that a hacker would need more “known” pages to be printed with the exact same method than has been printed in the entirety of humanity. In short perfect and uncrackable encryption.

Now to return to scaling for a moment. The X, Y, and Z axis can be modified as I stated. This represents a huge modifier. For instance in 5 bits alone there is in excess of 132 possible layouts. (sorry I was very tired while writing this, I know it has to be more, but I cannot formulate all possible layouts with how tired I am (to damned excited!!)). Now there is some 'issues' with 5 bits  having “empty spots” if there is this scaling. We cannot possibly get all the different layouts of empty spots due to the inability to tell where they would be. This issue is greatly reduced at larger bit chain lengths. However it would be possible to just run all versions of 4 bits, 3 bits, and 2 bits. In practice it is probably not likely that such small chain lengths will be used, but instead we will see something like a megabyte reduced to as low as half a megabyte for total 'spots' for making something near 2 megabytes in total outcomes. 

I also have included in my invention a means to 'subdivide' sections which allows us a greater flexibility in total drive design. Since we can render this into a 2D format this is just a way to make a series of different drives work in line without any serious increases in costs. 

Now this physical drive will result in some interesting outcomes. I believe that our human mind is based upon this sort of 'physical drive formation' except that it uses far more 'empty space' and the structures are far more unique. In this case however our drives could be long, wide, or tall compared to an average drive, but will see significant size reductions in general. Simply put we use far less space to store the data, and therefore also we will see weight savings in all probability. 

While some unique shapes will happen this will not greatly affect storage as each drive will probably be enclosed in a structure which will allow it to be bar-coded or otherwise identified for use as needed. Not all set ups however will require dramatic size modifications, for instance if converted to a 2D or if it is arranged to have 'white space' via usage of a color (or colors) stretching it to conform to a standardized size.  


Amazingly my system can be fully integrated with a number of storage mediums. Take the standard hard drive with the “magnetic pits” they have. On a terabyte drive remove 10 bits or less in specific order, and now you have a potential huge hard-coded drive in addition to your standard magnetic drive.  And the difference is fully detectable with everything standard to current drives. 

Even theoretical drives such as the Race Track memory (IBM) or Memristor (HP) can be subjected to my system for improved memory capacity (hard-coded). Not only that but Scaling has implications in transmitted data where multiple transmission sources are used or simulated in use. 


The upsides is dramatically increased memory capacity, reduced total weight and space requirement's, and ultimately I think GREATLY reduced costs. Add to this long-term storage capabilities, incredible encryption levels, and the ability to add hard-coded data to existing storage mediums. 

The downsides include long read times, non-existent write times (up until the ability to recycle the drives is perfected, a 3D recycler?) after the first printing, and possibly large storage requirements if converted to electronic binary. 


Potential customers however abound. Banks store financial records for a very long time, as do law firms, security companies, securities companies, financial institutions in general, Governments, Hospitals, and more. Data storage is an expensive field, with typically high power requirements. My method only requires power when the drive is being read. 



Patent Pending!

[toc] | [next] | [standalone]

#2063

Awesome post. It's always fun to meet articulate kooks.

Michael Harrington wrote:

> I am announcing my creation, a 3 part invention pertaining to a Solid
> Physical Drive. Physical as in it is made up of small parts, not
> electronic in manner, but in shapes, colors, and the absence of
> physical parts (Called Scaling, see below)
> 
> After much research I have concluded that a Physical Drive using
> Colors, Shapes, and a 2 function aspect I call Scaling will greatly
> increase how much data can be stored in a given inch². It not only
> represents a means of storage in a smaller space but has strong
> encryption qualities. Finally it represents a means to replace
> existing Long-Term storage with a far more stable format.
> 
> The theories behind what I do shall be obvious to experts, when they
> see it. But let me try to describe it for laymen. I take a set of
> data and make a 3d (or 1d excepting less storage) representation of
> it. Via Scaling I can change the X axis, the Y axis, or the Z axis to
> certain extents to change the total possible outcomes. I can also
> exclude some portions entirely, leaving “Empty spots”.
> 
> Adding Colors, which by the way the Human Eye can see 10,000,000 of,
> we can vastly increase our pool. Colors are very small in size,
> smaller than the “Pits” in current magnetic based hard-drives. Memory
> currently takes up a space of about 2.4 microns by 2.1 microns. The
> visible light spectrum is approximately 400 to 700 nanometers in
> size. This is .4 to .7 Microns. Light currently affords a far greater
> potential memory density than standard magnetic memory. However 3D
> printing is not quite to that point, but we can easily squeeze in
> about an extra 10% in storage with just light alone at our current
> tech.
> 
> However this Scaling method is not done. Scaling in my invention also
> allows “empty spots” as defined above. A standard Pascals Triangle
> will be useful for math here. You can take a given line of binary,
> and then do the following:
> 
> First is the whole of the normal values, if 10 bits, then we have
> 1024 outcomes. Then we move to 9 bits and take one from the 10 bits.
> This is 9 bits with 10 possible variations. This is (2^9)*10. Next we
> move to 8 bits with 45 possible variations. This is (2^8)*45. Next 7
> bits with 120 variations (2^7)*120 and then we go on for (2^6)*210,
> (2^5)*252, (2^4)*210, (2^3)*120, (2^2)*45 and (2^1)*10. We get 58,024
> total outcomes or 15.824 (rounded) bits.
> 
> We can also just see the empty spots as spacers. Spacing out a
> sequence of 1mb would mean seeing it increase in size, but the
> addition of spacers would mean more potential outcomes. This would
> mean we would have a much larger effective memory size.
> 
> More so, we can turn 3D structures into 2D structures by just
> partitioning the layers separately. This means we can utilize shapes,
> scaling, and color into standard binary without due issue.
> 
> In a physical format we also find that shapes are detectable at very
> small sizes. For some technical reasons (We need to keep our detector
> reasonably small) we should keep this near the size of color. Shapes
> is a way to encode higher amounts of data as well as provide some
> unusually robust encryption capabilities. In fact the combined whole
> (Shapes, Colors, Scaling) makes encoded Gigabytes so astronomically
> huge in complexity that a hacker would need more “known” pages to be
> printed with the exact same method than has been printed in the
> entirety of humanity. In short perfect and uncrackable encryption.
> 
> Now to return to scaling for a moment. The X, Y, and Z axis can be
> modified as I stated. This represents a huge modifier. For instance
> in 5 bits alone there is in excess of 132 possible layouts. (sorry I
> was very tired while writing this, I know it has to be more, but I
> cannot formulate all possible layouts with how tired I am (to damned
> excited!!)). Now there is some 'issues' with 5 bits  having “empty
> spots” if there is this scaling. We cannot possibly get all the
> different layouts of empty spots due to the inability to tell where
> they would be. This issue is greatly reduced at larger bit chain
> lengths. However it would be possible to just run all versions of 4
> bits, 3 bits, and 2 bits. In practice it is probably not likely that
> such small chain lengths will be used, but instead we will see
> something like a megabyte reduced to as low as half a megabyte for
> total 'spots' for making something near 2 megabytes in total
> outcomes.
> 
> I also have included in my invention a means to 'subdivide' sections
> which allows us a greater flexibility in total drive design. Since we
> can render this into a 2D format this is just a way to make a series
> of different drives work in line without any serious increases in
> costs.
> 
> Now this physical drive will result in some interesting outcomes. I
> believe that our human mind is based upon this sort of 'physical
> drive formation' except that it uses far more 'empty space' and the
> structures are far more unique. In this case however our drives could
> be long, wide, or tall compared to an average drive, but will see
> significant size reductions in general. Simply put we use far less
> space to store the data, and therefore also we will see weight
> savings in all probability.
> 
> While some unique shapes will happen this will not greatly affect
> storage as each drive will probably be enclosed in a structure which
> will allow it to be bar-coded or otherwise identified for use as
> needed. Not all set ups however will require dramatic size
> modifications, for instance if converted to a 2D or if it is arranged
> to have 'white space' via usage of a color (or colors) stretching it
> to conform to a standardized size.
> 
> Amazingly my system can be fully integrated with a number of storage
> mediums. Take the standard hard drive with the “magnetic pits” they
> have. On a terabyte drive remove 10 bits or less in specific order,
> and now you have a potential huge hard-coded drive in addition to
> your standard magnetic drive.  And the difference is fully detectable
> with everything standard to current drives.
> 
> Even theoretical drives such as the Race Track memory (IBM) or
> Memristor (HP) can be subjected to my system for improved memory
> capacity (hard-coded). Not only that but Scaling has implications in
> transmitted data where multiple transmission sources are used or
> simulated in use.
> 
> The upsides is dramatically increased memory capacity, reduced total
> weight and space requirement's, and ultimately I think GREATLY
> reduced costs. Add to this long-term storage capabilities, incredible
> encryption levels, and the ability to add hard-coded data to existing
> storage mediums.
> 
> The downsides include long read times, non-existent write times (up
> until the ability to recycle the drives is perfected, a 3D recycler?)
> after the first printing, and possibly large storage requirements if
> converted to electronic binary.
> 
> Potential customers however abound. Banks store financial records for
> a very long time, as do law firms, security companies, securities
> companies, financial institutions in general, Governments, Hospitals,
> and more. Data storage is an expensive field, with typically high
> power requirements. My method only requires power when the drive is
> being read.
> 
> Patent Pending!

[toc] | [prev] | [next] | [standalone]

#2065

I was trolled. Damn, and double damn! My snark content is to low, I am utterly defeated! As in he cut my feet off! That damn troll! *cry*

[toc] | [prev] | [next] | [standalone]

#2084

On Monday, November 4, 2013 6:02:43 PM UTC-6, Michael Harrington wrote:
> I am announcing my creation, a 3 part invention pertaining to a Solid Physical Drive. Physical as in it is made up of small parts, not electronic in manner, but in shapes, colors, and the absence of physical parts (Called Scaling, see below)
> 
> 
> 
> After much research I have concluded that a Physical Drive using Colors, Shapes, and a 2 function aspect I call Scaling will greatly increase how much data can be stored in a given inch². It not only represents a means of storage in a smaller space but has strong encryption qualities. Finally it represents a means to replace existing Long-Term storage with a far more stable format. 
> 
> 
> 
> 
> 
> 
> 
> The theories behind what I do shall be obvious to experts, when they see it. But let me try to describe it for laymen. I take a set of data and make a 3d (or 1d excepting less storage) representation of it. Via Scaling I can change the X axis, the Y axis, or the Z axis to certain extents to change the total possible outcomes. I can also exclude some portions entirely, leaving “Empty spots”.
> 
> 
> 
> Adding Colors, which by the way the Human Eye can see 10,000,000 of, we can vastly increase our pool. Colors are very small in size, smaller than the “Pits” in current magnetic based hard-drives. Memory currently takes up a space of about 2.4 microns by 2.1 microns. The visible light spectrum is approximately 400 to 700 nanometers in size. This is .4 to .7 Microns. Light currently affords a far greater potential memory density than standard magnetic memory. However 3D printing is not quite to that point, but we can easily squeeze in about an extra 10% in storage with just light alone at our current tech. 
> 
> 
> 
> However this Scaling method is not done. Scaling in my invention also allows “empty spots” as defined above. A standard Pascals Triangle will be useful for math here. You can take a given line of binary, and then do the following: 
> 
> 
> 
> First is the whole of the normal values, if 10 bits, then we have 1024 outcomes. Then we move to 9 bits and take one from the 10 bits. This is 9 bits with 10 possible variations. This is (2^9)*10. Next we move to 8 bits with 45 possible variations. This is (2^8)*45. Next 7 bits with 120 variations (2^7)*120 and then we go on for (2^6)*210, (2^5)*252, (2^4)*210, (2^3)*120, (2^2)*45 and (2^1)*10. We get 58,024 total outcomes or 15.824 (rounded) bits. 
> 
> 
> 
> We can also just see the empty spots as spacers. Spacing out a sequence of 1mb would mean seeing it increase in size, but the addition of spacers would mean more potential outcomes. This would mean we would have a much larger effective memory size. 
> 
> 
> 
> More so, we can turn 3D structures into 2D structures by just partitioning the layers separately. This means we can utilize shapes, scaling, and color into standard binary without due issue. 
> 
> 
> 
> In a physical format we also find that shapes are detectable at very small sizes. For some technical reasons (We need to keep our detector reasonably small) we should keep this near the size of color. Shapes is a way to encode higher amounts of data as well as provide some unusually robust encryption capabilities. In fact the combined whole (Shapes, Colors, Scaling) makes encoded Gigabytes so astronomically huge in complexity that a hacker would need more “known” pages to be printed with the exact same method than has been printed in the entirety of humanity. In short perfect and uncrackable encryption.
> 
> 
> 
> Now to return to scaling for a moment. The X, Y, and Z axis can be modified as I stated. This represents a huge modifier. For instance in 5 bits alone there is in excess of 132 possible layouts. (sorry I was very tired while writing this, I know it has to be more, but I cannot formulate all possible layouts with how tired I am (to damned excited!!)). Now there is some 'issues' with 5 bits  having “empty spots” if there is this scaling. We cannot possibly get all the different layouts of empty spots due to the inability to tell where they would be. This issue is greatly reduced at larger bit chain lengths. However it would be possible to just run all versions of 4 bits, 3 bits, and 2 bits. In practice it is probably not likely that such small chain lengths will be used, but instead we will see something like a megabyte reduced to as low as half a megabyte for total 'spots' for making something near 2 megabytes in total outcomes. 
> 
> 
> 
> I also have included in my invention a means to 'subdivide' sections which allows us a greater flexibility in total drive design. Since we can render this into a 2D format this is just a way to make a series of different drives work in line without any serious increases in costs. 
> 
> 
> 
> Now this physical drive will result in some interesting outcomes. I believe that our human mind is based upon this sort of 'physical drive formation' except that it uses far more 'empty space' and the structures are far more unique. In this case however our drives could be long, wide, or tall compared to an average drive, but will see significant size reductions in general. Simply put we use far less space to store the data, and therefore also we will see weight savings in all probability. 
> 
> 
> 
> While some unique shapes will happen this will not greatly affect storage as each drive will probably be enclosed in a structure which will allow it to be bar-coded or otherwise identified for use as needed. Not all set ups however will require dramatic size modifications, for instance if converted to a 2D or if it is arranged to have 'white space' via usage of a color (or colors) stretching it to conform to a standardized size.  
> 
> 
> 
> 
> 
> Amazingly my system can be fully integrated with a number of storage mediums. Take the standard hard drive with the “magnetic pits” they have. On a terabyte drive remove 10 bits or less in specific order, and now you have a potential huge hard-coded drive in addition to your standard magnetic drive.  And the difference is fully detectable with everything standard to current drives. 
> 
> 
> 
> Even theoretical drives such as the Race Track memory (IBM) or Memristor (HP) can be subjected to my system for improved memory capacity (hard-coded). Not only that but Scaling has implications in transmitted data where multiple transmission sources are used or simulated in use. 
> 
> 
> 
> 
> 
> The upsides is dramatically increased memory capacity, reduced total weight and space requirement's, and ultimately I think GREATLY reduced costs. Add to this long-term storage capabilities, incredible encryption levels, and the ability to add hard-coded data to existing storage mediums. 
> 
> 
> 
> The downsides include long read times, non-existent write times (up until the ability to recycle the drives is perfected, a 3D recycler?) after the first printing, and possibly large storage requirements if converted to electronic binary. 
> 
> 
> 
> 
> 
> Potential customers however abound. Banks store financial records for a very long time, as do law firms, security companies, securities companies, financial institutions in general, Governments, Hospitals, and more. Data storage is an expensive field, with typically high power requirements. My method only requires power when the drive is being read. 
> 
> 
> 
> 
> 
> 
> 
> Patent Pending!

Way too vague. As is, sounds like a bunch of nonsense, honestly...

[toc] | [prev] | [next] | [standalone]

#2086

Way to vague?

Color = possible outcomes (human eye alone 32 bits)

Shapes = possible outcomes (4 length, 1 width, 1 height x 6 peices versus 3 length, 2 width, 1 height x 5 +.... the possibilities increase exponantionally huge and fast)

Scaling, 5 bits can be arranged in excess of 500 different patterns (I just woke up for bathroom, sorry not precise) which is much larger than the 5 bits. This increases exponantionally with the number of bits (but will probably be held down from some outcomes at full size)

Subdividing in all of this will also affect total drive size in a net positive manner.



This all made with plastics, metals, or other materials. In the nanoscale.

In short a memory drive with well in excess of 3 times the density of existing memory drives.

[toc] | [prev] | [next] | [standalone]

#2087

Short version (not the provisional patent version)

A hard drive made up of physical parts, such as plastics or metals.

Colors can be used to encode more data than a standard hard drive. 3D printing is close to making 'nodes' smaller than current magnetic drive pits, though color 3D printing has a few more years to go.

shapes inside a color format can, mattering how they are utilized, result in more data per square inch or result in serious encryption.

By altering the max length, height, and width of a given drive (or the equivalent if working in 1D or 2D) you can dramatically increase the possible outcomes while accepting some drives will differ in size if in 3D. Subdividing can further allow for higher data yeilds.

Further you can, since we are working in the physical realm, leave some areas empty instead of filling them. This further increases possible outcomes. Possible outcomes in this regards is potential data sizes. 8 otcomes is 3 bits, 1024 outcomes is 10 bits. The math is log(possible outcomes) / log(2).

Combining all three has allowed me to demonstrate up to 2 times the capacity of conventional drives with a strong possibility of exceeding that. The systen is akin to hardcoding except it will be far cheaper than conventional methods. The proces can also be utilized on most, if not all, memory models to add extra total capacity (albiet a hard-coded amount) in large sums in exchange for small amounts reduced from the memory type in question. This capacity is per inch squared of drive space.

For instance removing 1 bit from a terabyte drive allows for 5 bytes of hardcoded data. Removing two would dramatically increase this total (my computer wont model that high). This is probably near a kilobyte after a half dozen bits are removed and the pattern of removal designates what the value of the hard-coded bits are.

The system is fully compatible to convert to binary but will become larger in size with Shapes and Scaling. As 3D printing matures this will become far cheaper than regular memory types. Ironically the best demonstration tool for the system would be a box of lego's.

PATENT PENDING - this is not the write up of the patent, it covers a bit more ;)

I intend to monetize this rather than keep it. Ideal customers are banks and financial institutions, schools, hospitals, governments, data storage facilities, etc.




I hope this works better for you.

[toc] | [prev] | [next] | [standalone]

#2091

On Monday, November 4, 2013 6:02:43 PM UTC-6, Michael Harrington wrote:
> I am announcing my creation, a 3 part invention pertaining to a Solid Physical Drive. Physical as in it is made up of small parts, not electronic in manner, but in shapes, colors, and the absence of physical parts (Called Scaling, see below)
> 
> 
> 
> After much research I have concluded that a Physical Drive using Colors, Shapes, and a 2 function aspect I call Scaling will greatly increase how much data can be stored in a given inch². It not only represents a means of storage in a smaller space but has strong encryption qualities. Finally it represents a means to replace existing Long-Term storage with a far more stable format. 
> 
> 
> 
> 
> 
> 
> 
> The theories behind what I do shall be obvious to experts, when they see it. But let me try to describe it for laymen. I take a set of data and make a 3d (or 1d excepting less storage) representation of it. Via Scaling I can change the X axis, the Y axis, or the Z axis to certain extents to change the total possible outcomes. I can also exclude some portions entirely, leaving “Empty spots”.
> 
> 
> 
> Adding Colors, which by the way the Human Eye can see 10,000,000 of, we can vastly increase our pool. Colors are very small in size, smaller than the “Pits” in current magnetic based hard-drives. Memory currently takes up a space of about 2.4 microns by 2.1 microns. The visible light spectrum is approximately 400 to 700 nanometers in size. This is .4 to .7 Microns. Light currently affords a far greater potential memory density than standard magnetic memory. However 3D printing is not quite to that point, but we can easily squeeze in about an extra 10% in storage with just light alone at our current tech. 
> 
> 
> 
> However this Scaling method is not done. Scaling in my invention also allows “empty spots” as defined above. A standard Pascals Triangle will be useful for math here. You can take a given line of binary, and then do the following: 
> 
> 
> 
> First is the whole of the normal values, if 10 bits, then we have 1024 outcomes. Then we move to 9 bits and take one from the 10 bits. This is 9 bits with 10 possible variations. This is (2^9)*10. Next we move to 8 bits with 45 possible variations. This is (2^8)*45. Next 7 bits with 120 variations (2^7)*120 and then we go on for (2^6)*210, (2^5)*252, (2^4)*210, (2^3)*120, (2^2)*45 and (2^1)*10. We get 58,024 total outcomes or 15.824 (rounded) bits. 
> 
> 
> 
> We can also just see the empty spots as spacers. Spacing out a sequence of 1mb would mean seeing it increase in size, but the addition of spacers would mean more potential outcomes. This would mean we would have a much larger effective memory size. 
> 
> 
> 
> More so, we can turn 3D structures into 2D structures by just partitioning the layers separately. This means we can utilize shapes, scaling, and color into standard binary without due issue. 
> 
> 
> 
> In a physical format we also find that shapes are detectable at very small sizes. For some technical reasons (We need to keep our detector reasonably small) we should keep this near the size of color. Shapes is a way to encode higher amounts of data as well as provide some unusually robust encryption capabilities. In fact the combined whole (Shapes, Colors, Scaling) makes encoded Gigabytes so astronomically huge in complexity that a hacker would need more “known” pages to be printed with the exact same method than has been printed in the entirety of humanity. In short perfect and uncrackable encryption.
> 
> 
> 
> Now to return to scaling for a moment. The X, Y, and Z axis can be modified as I stated. This represents a huge modifier. For instance in 5 bits alone there is in excess of 132 possible layouts. (sorry I was very tired while writing this, I know it has to be more, but I cannot formulate all possible layouts with how tired I am (to damned excited!!)). Now there is some 'issues' with 5 bits  having “empty spots” if there is this scaling. We cannot possibly get all the different layouts of empty spots due to the inability to tell where they would be. This issue is greatly reduced at larger bit chain lengths. However it would be possible to just run all versions of 4 bits, 3 bits, and 2 bits. In practice it is probably not likely that such small chain lengths will be used, but instead we will see something like a megabyte reduced to as low as half a megabyte for total 'spots' for making something near 2 megabytes in total outcomes. 
> 
> 
> 
> I also have included in my invention a means to 'subdivide' sections which allows us a greater flexibility in total drive design. Since we can render this into a 2D format this is just a way to make a series of different drives work in line without any serious increases in costs. 
> 
> 
> 
> Now this physical drive will result in some interesting outcomes. I believe that our human mind is based upon this sort of 'physical drive formation' except that it uses far more 'empty space' and the structures are far more unique. In this case however our drives could be long, wide, or tall compared to an average drive, but will see significant size reductions in general. Simply put we use far less space to store the data, and therefore also we will see weight savings in all probability. 
> 
> 
> 
> While some unique shapes will happen this will not greatly affect storage as each drive will probably be enclosed in a structure which will allow it to be bar-coded or otherwise identified for use as needed. Not all set ups however will require dramatic size modifications, for instance if converted to a 2D or if it is arranged to have 'white space' via usage of a color (or colors) stretching it to conform to a standardized size.  
> 
> 
> 
> 
> 
> Amazingly my system can be fully integrated with a number of storage mediums. Take the standard hard drive with the “magnetic pits” they have. On a terabyte drive remove 10 bits or less in specific order, and now you have a potential huge hard-coded drive in addition to your standard magnetic drive.  And the difference is fully detectable with everything standard to current drives. 
> 
> 
> 
> Even theoretical drives such as the Race Track memory (IBM) or Memristor (HP) can be subjected to my system for improved memory capacity (hard-coded). Not only that but Scaling has implications in transmitted data where multiple transmission sources are used or simulated in use. 
> 
> 
> 
> 
> 
> The upsides is dramatically increased memory capacity, reduced total weight and space requirement's, and ultimately I think GREATLY reduced costs. Add to this long-term storage capabilities, incredible encryption levels, and the ability to add hard-coded data to existing storage mediums. 
> 
> 
> 
> The downsides include long read times, non-existent write times (up until the ability to recycle the drives is perfected, a 3D recycler?) after the first printing, and possibly large storage requirements if converted to electronic binary. 
> 
> 
> 
> 
> 
> Potential customers however abound. Banks store financial records for a very long time, as do law firms, security companies, securities companies, financial institutions in general, Governments, Hospitals, and more. Data storage is an expensive field, with typically high power requirements. My method only requires power when the drive is being read. 
> 
> 
> 
> 
> 
> 
> 
> Patent Pending!

Problem is, you haven't really explained the important details of the mechanisms at work here. Just broad statements with the wave of the hand, nothing more. Tell you what, once you've obtained a patent, come back and post the details of the accepted submission and I'll take another look. Until then, I've got better things to do than entertain pie-in-the-sky claims.

[toc] | [prev] | [next] | [standalone]

#2092

I did file a provisional patent. 

What pie in the sky, this is supposed to be a smart persons group... I gave enough detail here where my lawyer understood it when I went to him and where an electrical engineer understood it when I explained it to him.

[toc] | [prev] | [next] | [standalone]

#2093

On Friday, November 8, 2013 12:41:31 PM UTC-6, Michael Harrington wrote:
> I did file a provisional patent. 
> 
> 
> 
> What pie in the sky, this is supposed to be a smart persons group... I gave enough detail here where my lawyer understood it when I went to him and where an electrical engineer understood it when I explained it to him.

Great, then perhaps you could convince them to post *their* explanation of how the system is supposed to work, because yours doesn't seem to be getting through to anyone here.

[toc] | [prev] | [next] | [standalone]

#2095

Bet if I put a reward down tons would, alas I wont be a welfare source.

How about asking questions?

[toc] | [prev] | [next] | [standalone]

#2099

Michael Harrington wrote:
>
> How about asking questions?
>
Do you know Jules Gilbert?

[toc] | [prev] | [next] | [standalone]

#2100

On Friday, November 8, 2013 8:05:07 PM UTC-6, pfraser wrote:
> Michael Harrington wrote:
> 
> >
> 
> > How about asking questions?
> 
> >
> 
> Do you know Jules Gilbert?

Indeed.

[toc] | [prev] | [next] | [standalone]

#2101

Thw con artist? yeah big claims, wont show math, methods or software. He sucks and i should say worse about him.
 
I am not him, ask for clarifications, methods, math, etc

[toc] | [prev] | [next] | [standalone]

#2096

On 08.11.2013 19:41, Michael Harrington wrote:
> I did file a provisional patent.
>
> What pie in the sky, this is supposed to be a smart persons group... I gave enough detail here where my lawyer understood it when I went to him and where an electrical engineer understood it when I explained it to him.

That's not the point. The point is that there is no method to understand 
here because you confuse information with representation.

So here comes the question: Given an average harddisk, and an average 
data file, please explain an application that compresses data by writing 
shapes and colors to this disk.

Answer: You made a category error. Just because a shape and a color is a 
piece of information does not mean that information can be "compressed" 
by representing them as shapes or colors. Information is an abstract 
principle and not bound to specific representation. What that 
representation is depends on the application, and cannot be described in 
general - simply because "information" is just that: "information with 
the specific represention abstracted away".

If you have four possible shapes and two possible colors, that makes 
three bits of information per piece. Nice and fine, but no compression. 
Even worse, fairly useless observation. If the shapes and colors are 
randomly distributed with an iid uniform distribution, it makes no 
difference how you represent that information: The number of bits you 
need is always the same. Making that step of course requires you to 
understand what a "bit" is. It is the information on the shape and color 
*without* the shape and color.

No matter what it is, if the distribution is uniform iid, no compressin 
possible.

Greetings,
	Thomas

[toc] | [prev] | [next] | [standalone]

#2098

Hi thomas

Excuse typos cause after rescuing 3 people from a rolled vehicle i have a thumb in an improvised brace. might be sprained or broke.

Wrist hurts also.

Anyhow this is not a binary language, instead it is a hardware method. since the math would be recognizable to compression experts posted here.

Let me demonstrate with a pascals triangle

1 1
1 2 1
1 3 3 1
1 4 6 4 1
1 5 10 10 5 1
1 6 15 20 15 6 1
1 7 21 35 35 21 7 1
1 8 28 56 70 56 28 8 1

Now forget colors for a second this is Scaling (one of two aspects where a physical location can be left open)

8 bits is 256. If you have 8 spots but only 7 magnetic pits you have 8 ways to arrange it, aka 3 hard-coded bits and 7 normal bits. 6 bits is 28 different variations or 4 additional bits. You should be able to resolve the rest.

Higher base amounts means more possible hard encoding.


Colors can be added, a 3D printer can reach 25 microns and this will improve over the life of the patent. Colors is not limited to human eyes 10 million different colors.

 Now while i talk of 3D structures that is patent protection. the best format will be 2d like current drives.

Shapes can be airb seperated, color seperated, elevation differenced or otherwise be made to stand out. the means is not critical.

Think graph paper. you can merge cells however you want. in theory each subsection ofa shape can have a seperate color but more likely it will be cheaper to have one color.

A 10x10 grid can hold a lot of single squares and/or mixed shapes it far exceeds the missinjg bit version of Scaling.

Scaling also allows us to redefine how high, wide, and long a drive can be. There is practical limitations (no one will make a drive 1 bit high, 1 wide, and 1 terabyte long!) but in general the variations possible is breathtaking.

There are other ways to increase the yeild, my patent covers them also. let me focus on these until people understand.

[toc] | [prev] | [next] | [standalone]

#2102

Hi,

once again, read my post slowly and carefully, and try to understand 
what I wrote. *Data compression* is the science of detecting and 
removing redundancy (and sometimes irrelevancy, for lossy compression) 
from data. How that data is represented is irrelevant. If you use bits 
or trits, or any other representation does not matter, the theory stays 
intact, just the unit changes.

Saying that you can "compress data by changing the representation" is as 
good as saying "you can shrink distances by measuring them in miles 
rather than kilometers". Yes, the numbers get smaller. No, you still 
need to walk the same distance.

The same "information change" happens if I use another basis for 
measuring information. If I store data in trits rather than bits (just 
to give you an example), the amount of information remains untouched, 
though I scale the unit by a factor of log 2 / log 3. Whether a 
trit-representation is physically advisable or not is another question 
(flash ram today stores more than one bit per cell, for example), and is 
a matter of a physical realisation. But it's not "data compression", 
which abstracts all this away and does not care.

Thus, whatever you do here is not related to compression nor information 
theory. It's probably related to data storage, likely data representation.

Once again, the error you made is a category error. You confuse 
information with how such information is represented. Information can be 
measured as the minimal number of binary questions necessary to retrieve 
a knowledge. Or also "trinary questions" (questions which allow three 
instead of two answers). How exactly does not even matter - that's the 
magic about it. It only changes the scale, but not the theory, and it 
doesn't compress anything.

Greetings,
	Thomas

[toc] | [prev] | [next] | [standalone]

#2103

Thomas Richter <thor@math.tu-berlin.de> wrote:

> what I wrote. *Data compression* is the science of detecting and 
> removing redundancy (and sometimes irrelevancy, for lossy compression) 
> from data. How that data is represented is irrelevant. If you use bits 
> or trits, or any other representation does not matter, the theory stays 
> intact, just the unit changes.
 
> Saying that you can "compress data by changing the representation" is as 
> good as saying "you can shrink distances by measuring them in miles 
> rather than kilometers". Yes, the numbers get smaller. No, you still 
> need to walk the same distance.

I think that isn't quite right, but it is so obvious that many ignore
it. If the data has a poor representation, then many compression
algorithms will find the redundancy in the representation.

Consider a file of random and uniformly distributed ASCII letters.
The redundancy is in the representation (ASCII) and not in the data
(the letters). 

LZW, for one, will find that in the same way it finds repeated strings,
and compress them down, not so far from the ideal. LZW does it without
knowing that it is compressing a poor representation of random data.

If you knew in advance that the data was uniform ASCII letters, you
might just encode them directly, but you don't always know that.

We often choose poor representation for convenience, though. Human
readable ASCII is nice, though often inefficient.

-- glen

[toc] | [prev] | [next] | [standalone]

#2109

Once in a while, in a bluemoon... I suspect this is the cycle of life, the rhythm / pattern which we can really compressed.

[toc] | [prev] | [next] | [standalone]

#2110

Do you know why they make the DVD shape like a DVD and not a donut ? The only storage that could do what you describe is a brain. If you make it like the brain you can't pattern it, as it is observable natural phenomenon, not something new or out of revolutionary.

[toc] | [prev] | [next] | [standalone]

#2111

The basic premise is:

1) Colors are encodable

2) 3D printers can print in color

3) The shape a physically constructed drive is in can be construed as a means to encode data.

4) physical representation can be varied in nature.



How can anyone contend otherwise?

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.compression

csiph-web