Message: Re: FieldManager handling Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

None Re: FieldManager handling 

Forum: Multithreading
Re: None FieldManager handling (Andrea Di Simone)
Re: Feedback Re: FieldManager handling (Andrea Dotti)
Re: None Re: FieldManager handling (Andrea Di Simone)
Re: Warning Re: FieldManager handling (Andrea Dotti)
Date: 06 Nov, 2012
From: Andrea Di Simone <Andrea Di Simone>

Hi Andrea,

ok now things make more sense.

I have one more question, though, concerning how putting my snippet in ConstructSlave would solve my problem.

Referring to my code snippet, theLogicalVolume is obtained from the one shared copy of the world volume. So theLogicalVolume is exactly the same for all threads. Is this correct? Then naively I would say that configuring the fields in ConstructSlave would just leave the volume with whatever configuration happened to be setup by the last thread to be initialized.

I have a similar problem understanding the migration documentation you provide, concerning for example the SD definition. In that case, you have a bunch of shared pointers to logical volumes, and in ConstructSlave each thread takes the same pointers and attaches to them different ("new") instances of SD. Shouldn't this lead to the volumes being associated to the SD defined by the last thread to be initialized? What am I missing? Are you doing something tricky under the hood?

Thanks for your help,


Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 Feedback: Re: FieldManager handling   (Andrea Dotti - 06 Nov, 2012)
(_ None: Re: FieldManager handling   (Andrea Di Simone - 07 Nov, 2012)
 Add Message Add Message
to: "Re: FieldManager handling"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews