Charm++ parallel programming system

[Jozsef Bakosi <jbakosi AT lanl.gov>]

Thanks, Tom,

I noticed this too. But I the "distance" between my
Main::Main(CkMigrateMessage* m) and CkStartCheckpoint() is pretty large
and I don't have a clean way of passing in an indicator, so I was hoping
to get that out of Charm++ via some API call.

Jozsef

On 03.19.2020 09:21, Tom Quinn wrote:
> What I do in ChaNGa is:
> 
> The Main object has an attribute "bIsRestarting".   The Main::Main(CkArgMsg*
> m) constructor sets this to "0", while the Main::Main(CkMigrateMessage* m)
> constructor (which is only called if restarting from a checkpoint) sets it
> to "1".  The callback method you pass to CkStartCheckpoint() can then test
> on "bIsRestarting".
> 
> Tom Quinn     Astronomy, University of Washington
> Internet:     
> trq AT astro.washington.edu
> Phone:                206-685-9009
> 
> On Thu, 19 Mar 2020, Jozsef Bakosi wrote:
> 
> > Hi folks,
> > 
> > Is there a way to detect from a Charm++ app that it just came back from
> > a restart and not just finished a checkpoint?
> > 
> > According to the manual:
> > 
> > cb will be invoked after the checkpoint is done, as well as when the
> > restart is complete:
> > 
> > CkCallback cb(CkIndex_Hello::SayHi(), helloProxy);
> > CkStartCheckpoint("log", cb);
> > 
> > When cb is called, I'd like to zero some counters if and only if it just
> > came back from a restart.
> > 
> > Thanks,
> > Jozsef