Conference Room SAD

[Thread display] [Reply] [New arrival display] [Word search] [Notes] [管理用]

No.	： 535
Title	： Re: SAD Update V1.1.1k64pre
Date	： 2017/07/20(Thu) 17:16:55
Name	： Akio Morita
URL	：

> Experimental:
> 1. Now keywords for MULT can take a list to represent the longitudinal
> profile of the parameters. Usage:
> LINE[“L”, “Q1”]={0.2, 0.6, 0.2];
> LINE[“K1”, “Q1”]={0.01, 0.05, 0.01};
> Remarks:
> - The keyword “L” must be given as a List to define the length of each
> segment. Other keywords are either a Real or a List with the same
> number of components as “L”.
> - If a key is a list, the value corresponding to the segment for “L” is
> taken. Otherwise the Real value is used commonly for all segments.
> - For a matching, the sum of the segments are used, and the resulting
> value is distributed to all segments, keeping the same profile.
> - Commands SAVE and RESET should work as expected.
> - In commands VAR, DISP, and element-value commands (such as Q1 K1
> 0.02), the summation of parameters are displayed.
> - TYPE shows the Listed parameters as List, but it is not readable by
> MAIN yet.
> - For LINE and Element functions, keyword$SUM returns the sum of the
> List if the value of keyword is a List. Otherwise, it returns the same
> value as the keyword. Example: LINE[“K1$SUM”, ”Q1”]. Setting to keyword$SUM
> is not yet implemented as expected.
> - Currently, the List keyword works only for MULT. However, it is not
> inhibited to set to other elements, which will cause unpredictable
> results.
> - OpticsPlot and GeometryPlot should work properly.
>
仕様レベルでのコメント

* 後方互換性を考慮するとGetter/Setter界面では、K1や L等の既設の変数は Master Variableとして振る舞わせ、分布等を設定する変数を接頭辞・接尾辞付きで新設する方が素直かと思います

* 暗に、積分値が non-zeroであることを想定してるようですが、wigglerの類や hericalなdeviceを考えると、master variableと form factorの概念は分離すべきだと思います

* herical deviceで、ROTATEに分布を持たせる場合、外部から指定するROTATEに対しては、加算的に振る舞って欲しいとか、Kn分布は乗算的に振る舞って欲しい等が有るので、パラメータ展開をframework側で行う場合、パラメータ毎にframeworkの振る舞いをカスタマイズできるべきです

* element内部のパラメータ分布のみを導入するなら、分布のハンドリングや計算時の展開処理は、tturn/ttruneレベルの driver framework側で行い、element実装コード側はパラメータ毎の振る舞い属性等の定義のみを行うようにすると、実装が一般化できると思います

** ある程度のelement interfaceの標準化が前提となりますが...

- Related List tree (Click ▼ to display all articles in a thread.）

▼

SAD Update V1.1.1k64pre

K. Oide

No.530

Re: SAD Update V1.1.1k64pre - Akio Morita 17/07/20-17:16 No.535
- Re^2: SAD Update V1.1.1k64pre - K. Oide 17/07/22-13:33 No.553
SAD Update V1.1.1k64_pre01 - K. Oide 17/07/23-20:08 No.556
Re: SAD Update V1.1.1k64pre - K. Oide 17/07/25-11:08 No.558
SAD Update V1.1.1k64_pre05 - K. Oide 17/07/26-01:44 No.560
SAD Update V1.1.1k64_pre07 - K. Oide 17/08/03-10:15 No.571
SAD Update V1.1.1k64_pre11 More on PROFILE, closed orbit with RADTAPER, etc. - K. Oide 17/08/24-15:30 No.601
SAD Update V1.1.1k64_pre15 - K. Oide 17/09/15-15:19 No.644
SAD Update V1.1.1k64 - K. Oide 17/11/20-22:31 No.681

- Reply Form (Reply to the above using the following.)

Name
E-Mail
Subject
Message
> > Experimental: > > 1. Now keywords for MULT can take a list to represent the longitudinal > > profile of the parameters. Usage: > > LINE[“L”, “Q1”]={0.2, 0.6, 0.2]; > > LINE[“K1”, “Q1”]={0.01, 0.05, 0.01}; > > Remarks: > > - The keyword “L” must be given as a List to define the length of each > > segment. Other keywords are either a Real or a List with the same > > number of components as “L”. > > - If a key is a list, the value corresponding to the segment for “L” is > > taken. Otherwise the Real value is used commonly for all segments. > > - For a matching, the sum of the segments are used, and the resulting > > value is distributed to all segments, keeping the same profile. > > - Commands SAVE and RESET should work as expected. > > - In commands VAR, DISP, and element-value commands (such as Q1 K1 > > 0.02), the summation of parameters are displayed. > > - TYPE shows the Listed parameters as List, but it is not readable by > > MAIN yet. > > - For LINE and Element functions, keyword$SUM returns the sum of the > > List if the value of keyword is a List. Otherwise, it returns the same > > value as the keyword. Example: LINE[“K1$SUM”, ”Q1”]. Setting to keyword$SUM > > is not yet implemented as expected. > > - Currently, the List keyword works only for MULT. However, it is not > > inhibited to set to other elements, which will cause unpredictable > > results. > > - OpticsPlot and GeometryPlot should work properly. > > > 仕様レベルでのコメント > > * 後方互換性を考慮するとGetter/Setter界面では、K1や L等の既設の変数は Master Variableとして振る舞わせ、分布等を設定する変数を接頭辞・接尾辞付きで新設する方が素直かと思います > > * 暗に、積分値が non-zeroであることを想定してるようですが、wigglerの類や hericalなdeviceを考えると、master variableと form factorの概念は分離すべきだと思います > > * herical deviceで、ROTATEに分布を持たせる場合、外部から指定するROTATEに対しては、加算的に振る舞って欲しいとか、Kn分布は乗算的に振る舞って欲しい等が有るので、パラメータ展開をframework側で行う場合、パラメータ毎にframeworkの振る舞いをカスタマイズできるべきです > > * element内部のパラメータ分布のみを導入するなら、分布のハンドリングや計算時の展開処理は、tturn/ttruneレベルの driver framework側で行い、element実装コード側はパラメータ毎の振る舞い属性等の定義のみを行うようにすると、実装が一般化できると思います > > ** ある程度のelement interfaceの標準化が前提となりますが...
URL
Password (alphanumeric characters within 8)
Subscribe Key (Enter the number of the right image)

- WebForum -

Name
E-Mail
Subject
Message > > Experimental: > > 1. Now keywords for MULT can take a list to represent the longitudinal > > profile of the parameters. Usage: > > LINE[“L”, “Q1”]={0.2, 0.6, 0.2]; > > LINE[“K1”, “Q1”]={0.01, 0.05, 0.01}; > > Remarks: > > - The keyword “L” must be given as a List to define the length of each > > segment. Other keywords are either a Real or a List with the same > > number of components as “L”. > > - If a key is a list, the value corresponding to the segment for “L” is > > taken. Otherwise the Real value is used commonly for all segments. > > - For a matching, the sum of the segments are used, and the resulting > > value is distributed to all segments, keeping the same profile. > > - Commands SAVE and RESET should work as expected. > > - In commands VAR, DISP, and element-value commands (such as Q1 K1 > > 0.02), the summation of parameters are displayed. > > - TYPE shows the Listed parameters as List, but it is not readable by > > MAIN yet. > > - For LINE and Element functions, keyword$SUM returns the sum of the > > List if the value of keyword is a List. Otherwise, it returns the same > > value as the keyword. Example: LINE[“K1$SUM”, ”Q1”]. Setting to keyword$SUM > > is not yet implemented as expected. > > - Currently, the List keyword works only for MULT. However, it is not > > inhibited to set to other elements, which will cause unpredictable > > results. > > - OpticsPlot and GeometryPlot should work properly. > > > 仕様レベルでのコメント > > * 後方互換性を考慮するとGetter/Setter界面では、K1や L等の既設の変数は Master Variableとして振る舞わせ、分布等を設定する変数を接頭辞・接尾辞付きで新設する方が素直かと思います > > * 暗に、積分値が non-zeroであることを想定してるようですが、wigglerの類や hericalなdeviceを考えると、master variableと form factorの概念は分離すべきだと思います > > * herical deviceで、ROTATEに分布を持たせる場合、外部から指定するROTATEに対しては、加算的に振る舞って欲しいとか、Kn分布は乗算的に振る舞って欲しい等が有るので、パラメータ展開をframework側で行う場合、パラメータ毎にframeworkの振る舞いをカスタマイズできるべきです > > * element内部のパラメータ分布のみを導入するなら、分布のハンドリングや計算時の展開処理は、tturn/ttruneレベルの driver framework側で行い、element実装コード側はパラメータ毎の振る舞い属性等の定義のみを行うようにすると、実装が一般化できると思います > > ** ある程度のelement interfaceの標準化が前提となりますが...
URL
Password	(alphanumeric characters within 8)
Subscribe Key	(Enter the number of the right image)