dolfin team mailing list archive
-
dolfin team
-
Mailing list archive
-
Message #24793
Re: Compile error with boost::iostream
That depends. With a mesh I get some 50% decrease, and dependent on the values
in a vector I can get much more.
I also found out that when a mesh is saved it is saved with _all_ its computed
connectivities. This can create rediculous large files. This was why I first
start looking into this. Not sure this is a feature or a bug. But I guess we
do not need to store more than the cell connectivities?
Johan
On Sunday October 23 2011 09:32:01 Anders Logg wrote:
> How much did the compression do? I thought it shouldn't have a big
> effect since the format is binary.
>
> --
> Anders
>
> On Sun, Oct 23, 2011 at 01:44:31AM -0700, Johan Hake wrote:
> > Hello!
> >
> > I got some very big files when saving using the TimeSeries format, so I
> > thought I added gzip support. After some tweaking I succeded locally.
> >
> > When pushed to my buildot I get a boost related compile error:
> > http://fenicsproject.org:8083/builders/dolfin-linux64-
> >
> > exp/builds/292/steps/dolfin%20build/logs/stdio
> >
> > Anyone know what this can originate from. I have boost 1.42 installed
> > locally and I guess the version is newer on the buildbot?
> >
> > Johan
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~dolfin
> > Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~dolfin
> > More help : https://help.launchpad.net/ListHelp
>
> _______________________________________________
> Mailing list: https://launchpad.net/~dolfin
> Post to : dolfin@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~dolfin
> More help : https://help.launchpad.net/ListHelp
Follow ups
References