JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for NEUTRINO-MC-SUPPORT Archives


NEUTRINO-MC-SUPPORT Archives

NEUTRINO-MC-SUPPORT Archives


NEUTRINO-MC-SUPPORT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

NEUTRINO-MC-SUPPORT Home

NEUTRINO-MC-SUPPORT Home

NEUTRINO-MC-SUPPORT  March 2013

NEUTRINO-MC-SUPPORT March 2013

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Request : Possibility to changing RandomGen to a wrapper?

From:

Costas Andreopoulos <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 5 Mar 2013 16:42:08 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (95 lines)

Dear Kotoyo.

> Thank you very much for answering my recent question, I finally got consistent result with my simulation and Genie output!

Good. Having read about how you go about simulating atmospheric neutrino events at IceCube, I was about to
offer adding a GENIE mode where *every* flux neutrino thrown towards the geometry is forced to interact. 
Would that make things easier for you?

> Today I have another issue about Random Generator.
> Currently GENIE is using TRandom3, but for our project we need to use our own random generator for several reasons (to control seed, consistency between other modules, parallel computing, etc).

I do not think this would work.

For one, GENIE uses PYTHIA which uses its own random number generator.
And, occasionally, we let ROOT draw random numbers from histograms (via TH1::GetRandom()) using its gRandom instance.

To make the GENIE MC jobs repeatable, the PYTHIA random number seed value and the gRandom seed value
are always set to be the same as the GENIE seed value.

Letting you replace GENIE's random number generator with your own generator is not enough
as you can not do the same with PYTHIA(6) and ROOT.

> I also have another minor request : inside destructor in some classes, there are cout calls and we can't make them silence.
> Would it be under control of logging system, or make silence mode as default?

These messages are in the destructors of some singletons. 
They can not go under the control of the logging system (a singleton itself) as, I think, there is
no guarantee regarding the order in which singletons are deleted and the logging system may no
longer be there to print out these messages.
They are not important messages so I will just comment them all out.

cheers
Costas

> I don't know where should I send these requests, if this ML is not appropriate please let me know.
> 
> Thank you,
> Kotoyo 
> 
> 
> On Mar 4, 2013, at 11:47 AM, Kotoyo Hoshina <[log in to unmask]> wrote:
> 
>> 
>> Dear all,
>> 
>> Thank you very much for answering my recent question, I finally got consistent result with my simulation and Genie output!
>> Today I have another issue about Random Generator.
>> 
>> Currently GENIE is using TRandom3, but for our project we need to use our own random generator for several reasons (to control seed, consistency between other modules, parallel computing, etc).
>> 
>> Is it possible to change RandomGen class to just a interface (wrapper) class, so that users can write their own random generator class?
>> Or even giving an option to RandomGen, for example, accepting user class inherited from TRandom3 would works for short term.
>> 
>> Here is the example :
>> 
>> class MyRandGen : public TRandom3 {…}
>> 
>> class RandomGen  {
>> 
>> public 
>>    void SetRandomGen(TRandom3 * random_ptr) { fRandom3 = random_ptr; }
>> 
>> }
>> 
>> void main() {
>> 
>>    MyRandGen * my_rand = new MyRandGen();
>>    RandomGen *rnd = RandomGen::Instance();
>>    rnd->SetRandomGen(my_rand);
>> 
>>    double random = rnd->RndGen()->Rndm();
>>    ….
>> 
>> }
>> 
>> If developers accept the idea, it would be nice if you could implement it to trunk in short term.
>> 
>> Thank you very much!
>> 
>> Kotoyo 
>> 
>> ---------------------------------------------------------
>> Kotoyo Hoshina
>> IceCube Assistant Scientist
>> Office : IceCube, 222 West Washington, Suite500, Madison, WI, 53703-2775 USA
>> Tel      : +1-(608) 890-0532
>> Mail    : [log in to unmask]
>> 
>> 
>> 
>> 

-- 
Scanned by iCritical.

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
July 2023
June 2023
May 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
October 2018
July 2018
May 2018
February 2018
January 2018
October 2017
May 2017
April 2017
March 2017
January 2017
December 2016
October 2016
September 2016
August 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
July 2015
May 2015
April 2015
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
April 2014
February 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
October 2012
April 2012
March 2012
September 2011
July 2011
June 2011
May 2011
December 2010
November 2010
October 2010
September 2010
June 2010
May 2010
April 2010
March 2010
February 2010
July 2009
June 2009
May 2009
April 2009
March 2009
January 2009
December 2008
June 2008
December 2007
August 2007
July 2007


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager