From: Hrvoje J. <hrv...@fs...> - 2015-11-25 11:26:39
|
Why don't we force gzip instead - in my experience, this is smaller than binary. I'd like to hear other opinions, but I am open to any good ideas HJ > On 25 Nov 2015, at 03:16, Martin Beaudoin <bea...@gm...> wrote: > > Hello, > > I am seriously considering disabling the ASCII writeFormat when meshes are larger than a predefined cells number. > > The idea is to still offer the ASCII writeFormat for small cases (which is useful for testing or training), but to mark it as unavailable when running simulations with serious size meshes, let's say larger than 10k cells. > > For larger meshes, the user would be forced to use the binary writeFormat. > > The specific mesh size would be defined at compile time, so site admins would be able to adjust this number if need be, but this number would not be overridable at runtime by users. > > The amount of storage space wasted on Foam/OpenFOAM meshes and solutions ASCII files is just too important. > > Thank you for your comments on this "radical" idea. > > Martin > > ------------------------------------------------------------------------------ > Go from Idea to Many App Stores Faster with Intel(R) XDK > Give your users amazing mobile app experiences with Intel(R) XDK. > Use one codebase in this all-in-one HTML5 development environment. > Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs. > http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140 > _______________________________________________ > Foam-extend-developers mailing list > Foa...@li... > https://lists.sourceforge.net/lists/listinfo/foam-extend-developers |