[Developers] optimising the size of checkpoints

[Thomas Radke]

Erik Schnetter wrote:
> Since the tags are tables, it would need to be checkpoint=0 or 
> checkpoint="no" (with quotes).  I would prefer the former, which would 
> make it CCTK_INT, the same as boolean parameters.

Sounds good to me. Would it also make sense to code in the integer how 
many timelevels should be checkpointed ?


> How much would be saved?  Did you try estimating what fraction of data 
> is unnecessary?

Well, you people doing productions runs tell me. Christian estimates a 
reduction of ~30-40% (which sounds a bit too much to me) but that was 
probably with Carpet::enable_all_storage left to "yes", Christian ? It 
would also need careful revision of analysis thorns before one can add 
those do-no-checkpoint tags to grid variables. But as a start I'll 
prepare a patch which implements such tags and also adds the necessary 
logic to the existing checkpoint methods.


-- 
Cheers, Thomas.