Re: [fluka-discuss]: ROT-DEFI indices and names
Yes this information is redundant and necessary at the moment unless the
code has changed in the last year.
Best
Vittorio
On Fri, Sep 26, 2014 at 10:46 AM, Timotheus Cooijmans <tim.cooijmans_at_cern.ch
> wrote:
> Thanks again Vittorio. In your example, you give different indices to
> differently-named cards, and identical indices to identically-named cards.
> The information conveyed to FLUKA by the index and name fields is
> redundant, and I was hoping to eliminate the redundancy by not having to
> specify an index, instead letting FLUKA choose an index for me. For
> hand-crafted inputs this is not so much an issue, but it complicates the
> process of automatically generating/manipulating an input. If I want to
> generate named ROT-DEFI cards, it looks like I will have to generate both
> an index and a name, and ensure both are unique in the input. Can you
> confirm this?
>
> Thanks,
> Tim
> ------------------------------
> *From:* Vittorio Boccone [dr.vittorio.boccone_at_ieee.org]
> *Sent:* Thursday, September 25, 2014 14:05
> *To:* Timotheus Cooijmans
> *Cc:* fluka-discuss_at_fluka.org
> *Subject:* Re: [fluka-discuss]: ROT-DEFI indices and names
>
> Hi Tim,
> the name of the ROT-DEFI is specified in the SDUM. About WHAT(1) you are
> hitting/discovering one for the usual what in which you can specify more
> parameters using a single WHAT. The leading (leftmost) digit is used to
> specify the axis around which the rotations are performed. The rest of the
> digits are used to give an index to the ROT-DEFI. It's mostly for back
> compatibility but I think there are also some CARD which are still using
> it.
>
> I attach an example (in free format)
>
> Best,
> Vittorio
>
> * Element: MCBCH.6R8.B1
>
> * L_x = 72.9926, L_y = -30.3194, L_z = 22802, C_x = 72.9926, C_y =
> -30.3194, C_z = 22747, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 101., 0.00000000000000, 0.00000000000000, -72.99260241836652,
> 30.31943314570012, -22746.97021779615898, tMCBCH6
>
> ROT-DEFI , 101., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -11500.00000000000000, tMCBCH6
>
> *
>
> * Element: MQML.6R8.B1
>
> * L_x = 72.9924, L_y = -30.3195, L_z = 23301.2, C_x = 72.9924, C_y
> = -30.3195, C_z = 23061.2, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 102., 0.00000000000000, 0.00000000000000, -72.99244714970530,
> 30.31949528173006, -23061.17020477964979, tMQML6
>
> ROT-DEFI , 102., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -12500.00000000000000, tMQML6
>
> *
>
> * Element: MQM.6R8.B1
>
> * L_x = 72.9923, L_y = -30.3194, L_z = 23677.9, C_x = 72.9923, C_y
> = -30.3194, C_z = 23507.9, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 103., 0.00000000000000, 0.00000000000000, -72.99228859386733,
> 30.31943303341426, -23507.87023291741934, tMQM6
>
> ROT-DEFI , 103., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -12000.00000000000000, tMQM6
>
> *
>
> * Element: MQM.A7R8.B1
>
> * L_x = 72.9915, L_y = -30.3195, L_z = 26391.1, C_x = 72.9915, C_y
> = -30.3195, C_z = 26221.1, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 104., 0.00000000000000, 0.00000000000000, -72.99146459134636,
> 30.31946740678214, -26221.07028312080365, tMQMA7
>
> ROT-DEFI , 104., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -12000.00000000000000, tMQMA7
>
> *
>
> * Element: MQM.B7R8.B1
>
> * L_x = 72.9914, L_y = -30.3195, L_z = 26767.8, C_x = 72.9914, C_y
> = -30.3195, C_z = 26597.8, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 105., 0.00000000000000, 0.00000000000000, -72.99139858225163,
> 30.31950500052763, -26597.77027337543404, tMQMB7
>
> ROT-DEFI , 105., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -12000.00000000000000, tMQMB7
>
> *
>
> * Element: MCBCV.7R8.B1
>
> * L_x = 72.9913, L_y = -30.3195, L_z = 26877.1, C_x = 72.9913, C_y
> = -30.3195, C_z = 26822.1, a_y = 0
>
> * ..+....1....+....2....+....3....+....4....+....5....+....6....+....7...
>
> ROT-DEFI , 106., 0.00000000000000, 0.00000000000000, -72.99130772555418,
> 30.31948541226025, -26822.07022732733822, tMCBCV7
>
> ROT-DEFI , 106., 0.00000000000000, 0.00000000000000, 0.00000000000000,
> 0.00000000000000, -11500.00000000000000, tMCBCV7
>
> On Thu, Sep 25, 2014 at 10:23 AM, Timotheus Cooijmans <
> tim.cooijmans_at_cern.ch> wrote:
>
>> Hello FLUKA experts,
>>
>> How do ROT-DEFI indices and names interact? I'm trying to
>> (programmatically) define a composite rototranslation (i.e. multiple
>> ROT-DEFI cards with the same identifier). I'd like to only have to provide
>> a name and not worry about the index. Here's the relevant manual excerpt:
>>
>> WHAT(1) : assigns a transformation index and the corresponding
>> rotation axis
>> =< 0.0 : the card is ignored if SDUM is empty, otherwise
>> SDUM is
>> kept as the rotation name, and the first free
>> rotation
>> number is used
>> > 1000 : interpreted as j + i * 1000
>> > 100 and < 1000 : interpreted as i + j * 100
>> (note the inversion of i and j!)
>> > 0 and =< 100 : interpreted as i, and j assumed to be = 0
>> where i = index of the rotation
>> j = 1 rotation with respect to x axis
>> = 2 rotation with respect to y axis
>> = 0 or 3 rotation with respect to z axis
>> (see Note 4)
>> Default = 0.0 (no transformation defined)
>>
>> Two things puzzle me about this:
>> * I can only give the transformation a name if I set WHAT(1) <= 0, but
>> then I can't choose j.
>> * Two cards with the same name and unspecified index (WHAT(1) = 0) will
>> be assigned different indices.
>>
>> It would be great if someone could shed some light on this situation.
>>
>> Many thanks,
>> Tim
>>
>
>
Received on Fri Sep 26 2014 - 13:08:57 CEST
This archive was generated by hypermail 2.3.0
: Fri Sep 26 2014 - 13:08:58 CEST