charm AT lists.siebelschool.illinois.edu

Subject: Charm++ parallel programming system

List archive

Re: [charm] Further per-node / per proc initialization after mainchare completion

From: Evan Ramos <evan AT hpccharm.com>
To: charm <charm AT lists.cs.illinois.edu>
Subject: Re: [charm] Further per-node / per proc initialization after mainchare completion
Date: Thu, 7 May 2020 19:35:46 -0500
Authentication-results: illinois.edu; spf=none smtp.mailfrom=evan AT hpccharm.com; dkim=pass header.d=hpccharm-com.20150623.gappssmtp.com header.s=20150623; dmarc=none

Hi Shenghao,

For your use case, instead of initproc and initnode functions, try creating a group or a nodegroup respectively and sending a broadcast to it from the mainchare's constructor.

Regards,

Evan A. Ramos

Software Engineer

Charmworks, Inc.

On Thu, May 7, 2020 at 2:46 PM Shenghao Yang <me AT shenghaoyang.info> wrote:

Hello,

I'm wondering if there is a way to run initproc / initnode like functions after completion of mainchares (after the readonly global variable initialization is done by the mainchares) because I'll need to run some memory initialization routines that depend on the readonly global variables computed by the mainchare.

Or, is there some way for initproc / initnode functions to access the arguments that are typically provided to mainchares? Encoding constants into the function bodies might work, but I'd like to see if there is something more elegant.

Hopefully I'm not missing something that's in the manual - that'd be a pretty bad case of PEBCAK.

Thanks!

Shenghao

[charm] Further per-node / per proc initialization after mainchare completion, Shenghao Yang, 05/07/2020
- Re: [charm] Further per-node / per proc initialization after mainchare completion, Evan Ramos, 05/07/2020